Post-refresh configuration & deployment strategy for Salesforce Revenue Cloud (RCA) in Dev Sandboxes
Hi everyone,
We need guidance on managing Salesforce Revenue Cloud Advanced (RCA) configuration data across sandbox environments:
1. Post-Refresh Data Seeding (Dev Sandboxes) When refreshing Developer sandboxes, configuration data (Products, Catalogs, Attributes, Price Books, Price Rules) is not copied over.
- What tools do you recommend for seeding this data ?
- How do you manage External IDs across environments to preserve parent-child relationships and avoid duplicates?
2. Deployment Strategy (Dev → Next Environments) Our vendor team deploys via VS Code and Dell Boomi.
- How do you split deployment tasks between metadata tools (VS Code for Context Definitions, Expression Sets, Decision Tables) and data integration tools
- What is the required deployment order and post-deployment steps (e.g., Sync Pricing Data / Decision Table refreshes, Product Index rebuilds) to avoid runtime errors like "Price Not Found"?
Thanks for your advice!
#Salesforce Revenue Cloud
When refreshing developer sandboxes where core configuration data like products, catalogs, attributes, price books, and price rules do not carry over, you should leverage reliable data migration utilities such as Salesforce Data Loader, SFDX data tools, or specialized CPQ seeding scripts. To maintain parent-child hierarchies and prevent duplicate records across environments, ensure that you prepopulate and maintain consistent external IDs across all catalog and pricing records before executing bulk data inserts.
For your deployment workflow moving from development to downstream environments, cleanly divide your tasks by deploying metadata components like context definitions, expression sets, and decision tables via VS Code first, while using integration platforms like Dell Boomi to handle your underlying pricing data records. Following a strict sequence that deploys your metadata structure prior to your pricing data records ensures that dependent references resolve correctly from the start.
Execute essential post-deployment steps to prevent runtime calculation issues such as "Price Not Found" errors. You must refresh your decision tables, synchronize pricing data, and trigger product index rebuilds in the target environment so that runtime calculations align properly against your newly deployed context definitions and catalog hierarchies.
