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!
The ProductCategoryProduct object is a junction between Product2 and ProductCategory. You might not be able to map it as a flat attribute on an existing node — it needs its own CategoryProduct node in the context definition, and then a cross-context attribute mapping to bridge the value into SalesTransactionItem.
There isn't specific guidance on mapping the "ProductCategoryProduct" junction object into a Sales Transaction Context Definition or whether it should be modeled as a separate child node versus a direct attribute on "SalesTransactionItem". This scenario might require further validation in your org.
Try creating a dedicated child node for "ProductCategoryProduct" under "Product" or "SalesTransactionItem" to see if it resolves the mapping issue and allows stable Map Data configuration.
