Salesforce Revenue Cloud Management is a powerful tool for automating your sales process, but its complexity can lead to challenges if configurations are not handled correctly. This guide will help you enable Partner Users to create quotes and address common issues in Salesforce CPQ with actionable steps.
PARTNER USERS
If you set up an Experience site and enable Partner Users, you need to do two things to enable them to create a Quote:
To allow Partner Users in an Experience Site to create a quote, you need to perform two key configurations:
. Adjust Sharing Settings
- Navigate to Setup > Security > Sharing Settings.
- Update the Sales Transaction Type setting to Public Read for both internal and external users.
2. Update Permission Sets
- Go to Setup > Permissions.
- Locate the Custom Partner Community User Permission Set.
Add Read access to the Sales Transaction Type object
Why These Steps Matter
The Sales Transaction Type object is critical because Salesforce CPQ uses it to call the Pricing Procedure in the background. Without proper access, Partner Users won’t be able to create quotes. It’s worth noting that Salesforce might revise the default settings in upcoming releases, so stay updated to avoid disruptions.
MISCELLANEOUS TIPS FOR COMMON CPQ ISSUES
Products Not Available for Selection
Sync Your Products:
Every time you add a product or modify an attribute that affects pricing, you must:
- Go to Setup > Feature Settings > Salesforce Pricing > Salesforce Pricing Setup.
- Click the Sync button.
This step ensures your product appears in the product selector.
Refresh Pricing Decision Tables:
Salesforce allows 20 refreshes per hour for decision tables. If you’ve exceeded the limit, you’ll need to wait before performing another refresh. To save time:
- Refresh only the relevant decision table by navigating to: Setup > Decision Tables > [Select Your Decision Table] > Click Refresh (top right).
Verify Product and Procedure Mapping:
Ensure the following are set up correctly:
- Product Discovery Procedure: Fully map all necessary attributes.
- Default Product Discovery Procedure: Confirm its accuracy.
- .Sales Context Pricing Procedure: Link it to both:
– The Product Discovery Procedure, and
– The Product Discovery Pricing Procedure
Be Patient:
After syncing, changes may take up to an hour to reflect in the system. If you don’t see your product in Browse Catalogs, wait before troubleshooting further.
Understanding Product Classification
In Salesforce RLM, terminology can sometimes be confusing:
- Product Attributes are assigned to Product Classifications.
Products themselves are assigned to Categories, not directly to Product Classifications
Price Book Entries and Product Selling Models
A single product can exist in a Price Book multiple times if it has different Product Selling Models. This provides flexibility when defining diverse selling strategies.
Managing Product Images
To enhance the user experience:
- Upload product images as Static Resources.
Use the generated URLs in the product details
PROBLEMS AND SOLUTION: TROUBLESHOOTING COMMON ISSUES
1: Why aren’t custom fields visible in the Qualification Procedure flow (Expression Set)?
A: You likely forgot to activate the Context Definition. After mapping fields and adding tags, always activate the definition to make fields available as variables in the flow.
2: Why does a bundle added to a quote display as one line without components?
A: While selecting the product from the catalog, click the gear icon to configure the product and view its components. This allows you to adjust options like the number of USB ports.
3: Why isn’t the Configure quick action visible on a Quote Line Item?
A: This often happens if you’re viewing the QLI record directly. Instead:
- Go to the Quote Line Items list.
- Click the caret icon at the end of the row to access options like View, Edit, Configure, or Delete.
4: Why don’t optional child products appear when adding a bundle via the Add Products button?
A: The Add Products button only adds required child products to the quote. For optional child products, use the Browse Catalogs button, which supports configurable bundles.
5: What does this error mean:
“Resolve error: Something went wrong while hydrating additional context fields: Cannot invoke industries.context.api.service.model.runtime.schema.impl.defaultimpl.DefaultContextRuntimeentityAttribute.getTags() because the return value of java.util.Map.get(Object) is null”?
A: Check the following configurations:
1.Context Definition Mappings:
Ensure mappings are accurate.
Avoid changing field types (e.g., Text to Picklist) after mappings are complete.
2.Custom Tags:
Ensure they’re mapped correctly. If unsure, use Generate All Mappings.
3.Default Mapping:
Confirm a default mapping exists in the Context Definition.
4.New Context Definition Versions:
If using a new version, link it to the Product Discovery Procedure and the Sales Transaction Procedure.
5.Decision Tables:
Ensure all decision tables are synced after making changes.
6.Attribute-Based Pricing:
Verify that this element in the Pricing Procedure is marked for output.
7.Permission Sets:
Ensure all required permissions are assigned to your profile.
KEY TAKEAWAYS
1.Organize Your Processes:
Regularly verify mappings, permissions, and procedural setups.
2.Sync and Refresh:
Sync products and decision tables after updates to prevent errors.
3.Understand Terminology:
Differentiate between Product Attributes, Classifications, Categories, and Selling Models.
4.Enable Seamless Access:
Ensure Partner Users and internal teams have the permissions they need.
By following these detailed steps and tips, you can streamline your Salesforce RLM setup and resolve common issues with confidence.