Skip to main content

フィード

Trailblazer 仲間と繋がりましょう。質問したり、質問に答えたりして、スキルを磨き、ネットワークを構築しましょう。
1 件の回答
  1. 今日、13:54

    Hi @Siddantapu Shyam Naga Prasad

    Please ensure that the Product, Type, and Case Reason fields have been added to the Case Detail section of the Product Support Case Layout.

    Note: There are two different Product fields available. Be sure to select the Product picklist field and not the Product lookup field.

0/9000

Hi everyone,

I'm currently working through the Trailhead module Implement Attribute-Based Pricing.

As part of the exercise, I updated the Default Pricing Procedure under Revenue Settings. After that, when I try to configure the product, I'm getting the following error:

"Something went wrong while running configuration rules. You can’t open the Product Configurator because the ConstraintEngineNodeStatus field either hasn’t been added to transaction line item objects or hasn’t been mapped to the active context definition. Your Salesforce admin can help with that."

Has anyone encountered this issue while following this Trailhead module? Could you please let me know what configuration I'm missing or what needs to be fixed?

Thanks in advance for your help!

 

unable to configure the product in product configuration in revenue cloud 

 

 

image.png

 

 

 

#Trailhead Challenges  #Revenue Cloud  #Salesforce Revenue Cloud

1 件の回答
0/9000

In an ongoing data cleanup process, we are beginning to turn attention to Trust accounts. We currently get updates imported daily via our broker dealer, who is getting the file from the aggregator (Albridge). The updates seek and match to a Person Account SSN.  

 

Looking at Trust accounts, certain ones (living trusts) will use the Trustee SSN rather than a separate TIN. Does anyone currently work this way, and how are you working to match the Person Account information separately from the Trust when they use the same identifier?

1 件の回答
  1. 今日、13:24

    We solved this with two tax ID fields and two separate imports for the same object. 

     

    Person Accounts store the SSN in one field (SSN__c). Trusts and other entities are business Accounts and store their tax ID in a different field (EIN__c). Two fields means the same number can live in both places without conflict. 

     

    Each row in our custodian feed says what type of client it is (Individual or Entity), so we split the file into two imports before matching. Individual rows only search Person Accounts on SSN__c. Entity (trust) rows only search business Accounts on EIN__c.  

     

    Example: Brenda's Person Account has 123-45-6789 in SSN__c. The Brenda Family Trust is a separate business Account with that same 123-45-6789 in EIN__c. When an update comes in for her individual brokerage account, it's flagged as an individual, so it only searches Person Accounts and finds Brenda. When an update comes in for the trust account, it's flagged as a trust, so it only searches business Accounts and finds the trust. Same number, no collision, because the flag decides where to look, not the number. 

     

    For this to work for you, data feed has to tell you which rows are trusts and which are individuals (a registration type or account type field, something like "individual" vs "revocable trust"). If it has that, you're set. 

0/9000

I am currently working on my Superbadge: Report Administration for Agentforce Readiness, and no matter the changes I make, I keep getting this error message:

The Open Opps Accts Ownership report isn't using the correct filters or isn't grouped as specified, by owner and owner active status (not account active status). Make sure you're using a type of filter that crosses objects and restricts the records displayed to only accounts with open opportunities. Review the Help article for resources related to this challenge.

I have followed the resource articles, and still cannot seem to find a solution for this. Has anyone come across this before?

#Service Cloud #Trailhead Superbadges #Agentforce
2 件の回答
0/9000
2 件の回答
0/9000

We can't find the new contract created from the 'Acme Sneakers Quote' with the expected values. Make sure the contract start date is today, the contract terms is 24 months, and the contract document was generated from the template. 

 

I am getting this error but i have done all steps correctly 

 

#Trailhead Challenges

2 件の回答
  1. 今日、13:05

    Ensure you're completing the challenge in the same Playground/org where you performed the setup.

0/9000

Hi everyone, 

I currently have navigation buttons set up in my Tableau dashboards, but I’d like to explore other ways to improve navigation and make the reports more intuitive for users.

What are the different approaches or best practices for enhancing navigation in Tableau dashboards beyond just using navigation buttons? For example, are there techniques involving sheet swapping, menus, filters, or creative layouts that can help users move through reports more smoothly?

I’d really appreciate suggestions, examples, or resources that highlight different navigation methods.

Thanks in advance! 

 

#Tableau Desktop & Web Authoring

6 件の回答
  1. 今日、12:51

    Hi! Here are 3 highly effective approaches to enhance dashboard navigation beyond simple buttons, along with official Tableau resources for best practices: 

     

    1. Filter Actions (Use Sheets as Filters)

    Instead of using generic quick filters, set up sheet-to-sheet filter actions. When a user clicks on a data point in one chart, it dynamically filters other related views.

    • Why it works: It allows users to naturally drill down into the data through interactive exploration rather than just clicking static menu options.

    2. Sheet Swapping (using Parameters & Layout Containers)

    If you have multiple views (e.g., Trend vs. Detail) but limited space, you can use a parameter to let users swap entire sheets dynamically within a container.

    • Why it works: It maximizes screen real estate and keeps the report incredibly clean and focused.

    3. URL Actions (Navigate Beyond Tableau)

    Use URL actions to send users to external web pages, internal portals, or other workbooks by dynamically embedding values (such as Product IDs) as parameters.

    • Why it works: It bridges the gap between discovering an insight in Tableau and taking the next business action in your other operational systems 

    Official Resources & Best Practices

    For detailed design principles regarding dashboard interactivity and layout sizing, these official Tableau guides are highly recommended:

     

      

     Hope this helps! 

0/9000

I have issues with creating leads through contact form. i m not sure where i m going wrong.

2 件の回答
  1. 今日、12:37

    Please share the any screenshot of the error meassage.

0/9000
3 件の回答
0/9000

Online it is posed that the Compulsory Info Session for Q3 Intro To Coding is next week (8/23). 

 

Is there a link available for this session yet? 

15 件の回答
0/9000