* Salesforce Revenue Cloud *

Hi everyone, I'm working on a Revenue Cloud business scenario in a Developer Edition org where I need to apply tax on a product based on a product's category.    I've extended the standard Sales Transaction Context Definition into a custom one. When I try to map a "Product Category" attribute on the SalesTransactionItem node to the ProductCategoryProduct object/field in Map Data, the mapping isn't going through — the field either doesn't appear as mappable, or the mapping doesn't save correctly.    Has anyone successfully mapped ProductCategoryProduct (junction object between Product2 and ProductCategory) into a Context Definition? Does this require creating a separate child Node for ProductCategoryProduct instead of adding it as a direct attribute on the existing Product/SalesTransactionItem node? Any guidance on the correct Node structure and relationship path would help a lot. Thanks in advance!   

@* Salesforce Revenue Cloud * 

Hi @* Salesforce Revenue Cloud *

, 

I need clarification on the data mapping between objects in Salesforce Revenue Cloud. 

For example, I created a custom field on both the Product and Quote Line objects and mapped the Product field to the Quote Line field. When I add a product using the Browse Catalog, the field is mapped correctly. However, if the Quote Line already exists and I click Reprice, the field is not updated. Is this the expected behavior?

I am trying to create a rule in Constraint Builder but when I try to add the product, I do not see all.   I have this product bundle that has three child components.   When I add the products, the child products are not showing up in the list.   all the products are active.    When I add the product and go to CML Editor, I do not see the child products either only this:  type Parent_Product : LineItem;

@* Salesforce Revenue Cloud * 

Has anyone encountered this error in the Salesforce Approval Process while working in RCA?

If you've seen this issue before, could you please share the root cause or how you resolved it? Any insights or suggestions would be greatly appreciated.

Thank you! 

When creating an attribute definition we forgot to specify the data type as text and because the picklist values were numbers, the data type was set by the platform to decimal(2). This of course causes issues with my constraint model and rules. Interestingly enough I can manually set the attribute to string and fix the values directly in the CML, but this is no a great practice and someone has to remember do this like forever. I attempted to back everything out, deleted it and clear the recycle bin, but I assume there's a platform cache somewhere (like this velocity trailhead talks about

) that still has the original API name and when I try to recreate the attribute definition with the original API name, the platform appends a 1 to the end of the API name.   

This is a brand new org and I'm using the feature code from the client's ERP so having a mismatch is a real pain in the neck to be doomed to from the beginning. Frankly, I would rather nuke the org and start fresh if this can't be resolved. I've asked all the smarties I know, but I know there are bigger smarties out there.  

Plaze Halp! Danka

Hi all, 

Sharing a setup guide our team put together for CML Explainability, in case it's useful for anyone here enabling it in their org. 

Quick recap for anyone who hasn't touched it yet: Explainability logs what the solver engine does during a configurator request – what actions it executes, how they relate to each other, how long each action took, and how variables changed. Available in the Revenue Cloud Operations Console under Configuration Logs, plus queryable via the DES Connect API. 

Setting it up involves a few pieces: 

• A permission set with the "Read and write configuration logs" system permission enabled (license type: Product Configuration User)
• Four Decision Explainability definitions in Setup: Application Subtype, Business Process Type, Explainability Action Definition, Explainability Action Version — each with specific field values

We wrote it all up here. Hope it will help. 

Thanks!