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.
フィード
- 最近の活動
- 作成日
- 承認された回答がある質問
- 承認された回答がない質問
- 未回答の質問
- Appexchage Apps
- Audience Studio
- Automation Studio
- B2B Commerce
- B2C Commerce
- Business Rules Engine
- Communications Cloud
- Consumer Goods Cloud
- Dataloader.io
- Datorama
- Digital Engagement
- Education Cloud
- Education Data Architecture
- Einstein Bots
- Email Marketing
- Experience Cloud
- Financial Services Cloud
- High Velocity Sales
- Higher Education
- Integration
- Interaction Studio
- Journey Builder
- K-12 Architecture Kit
- Manufacturing Cloud
- Marketing Cloud
- Mobile Publisher
- MuleSoft
- MuleSoft API Manager
- MuleSoft Anypoint Code Builder
- MuleSoft Anypoint Platform
- MuleSoft Anypoint Studio
- MuleSoft CloudHub / RTF / On-Prem / PCE / Gateway
- MuleSoft Composer
- MuleSoft Connectors / SDK / DevKit
- MuleSoft DataWeave
- MuleSoft Design Center / API Designer
- MuleSoft Exchange
- MuleSoft For Agentforce
- MuleSoft For Flow: Integration
- MuleSoft Integrations
- MuleSoft Training & Certification
- Nonprofit
- Nonprofit Cloud
- Nonprofit Success Pack
- Outbound Funds Module
- Pardot B2b Marketing Automation
- Program Management Module
- Quip
- Revenue Cloud
- Sales Cloud
- Sales Cloud Einstein
- Salesforce CPQ & Billing
- Salesforce Developer
- Salesforce Field Service
- Salesforce Health Cloud
- Salesforce Maps
- Salesforce Platform
- Salesforce Surveys
- Service Cloud
- Service Cloud Einstein
- Service Cloud Voice
- Slack Basics
- Slack Certified
- Slack Community
- Slack Developers
- Slack Workflow Builder
- Tableau APIs & Embedding
- Tableau Agent
- Tableau Cloud
- Tableau Community Updates
- Tableau Desktop & Web Authoring
- Tableau Mobile
- Tableau Next
- Tableau Prep
- Tableau Public
- Tableau Pulse
- Tableau Release Readiness Bulletins
- Tableau Server
- Automation
- AwesomeAdmins
- Data Management
- EducationHelp
- Formulas
- IdeaExchange
- New Releases
- NonprofitHelp
- Salesforce Developer
- SalesforceLive
- TrailblazerCommunityHelp
- TrailblazerDX
- Trailhead Challenges
- Trailhead Superbadges
- TrailheadGO
検索条件
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!
#Trailhead Challenges #Revenue Cloud #Salesforce Revenue Cloud
今日、13:35 Hi @Vasu Kasula, Please make sure Advanced Configurator is enabled, then add the ConstraintEngineNodeStatus mapping to the Context Definition.
Please refer below -
https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000TkvJb0AJ
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?
今日、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.
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今日、13:17 @Carl Novakovich, Please refer to the thread below, which discusses a similar issue.
https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000gUTox0AG
今日、13:08 @MUTHU JEEVA, Are you following a specific trailhead module or challenge? If so, please share the module link.
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
今日、13:05 Ensure you're completing the challenge in the same Playground/org where you performed the setup.
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
今日、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:
- Visual Analysis Best Practices (Tableau Visual Guidebook): https://www.tableau.com/ja-jp/learn/whitepapers/tableau-visual-guidebook
- 10 Best Practices for Building Effective Dashboards: https://www.tableau.com/ja-jp/learn/whitepapers/10-best-practices-building-effective-dashboards
Hope this helps!
I have issues with creating leads through contact form. i m not sure where i m going wrong.
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?