Before you're able to start deploying your CPQ configuration between environments, it's critical that you first get your CPQ config aligned in your environments. Having the building blocks in place before doing any additional CPQ development ensures you can easily track changes, avoid deploying duplicates and ensuring consistency across your entire Salesforce environment process.
Required: Running the external ID setup for your org(s) in Gearset
A core part of being able to sync your CPQ configuration is to have first run the Gearset external ID setup wizard on each of your orgs. Without this in place, Gearset cannot track and manage the deployment of your CPQ configuration and avoid duplicates from being deployed. You can read more about using Gearset new external ID setup wizard to easily add and populate the external ID field from our documentation.
Solution 1: As part of a full copy sandbox refresh
The cleanest way to make sure your full copy sandbox and production org CPQ configuration is perfectly in sync is via a full copy sandbox refresh.
Note: The setup requires you to do a full copy sandbox refresh so you should ensure that all necessary metadata and CPQ config that you care about from your full copy sandbox are in your production org before starting the process.
Step 1: Run the Gearset external ID setup on your Production org
Gearset will perform a metadata deployment to add its external ID field to CPQ and related standard CPQ objects, followed by a data deployment to populate its external ID field derived from the existing Salesforce record ID.
Step 2: Perform a full copy sandbox refresh to perfectly align it with production
Once the Gearset external ID has been successfully added and populated with the existing record IDs, you can now perform a full copy sandbox refresh. This will leave your Production and Full Copy Sandbox perfectly in sync.
Step 3: Deploy from dev to full copy sandboxes to production for better CPQ configuration deployments
You can seed existing CPQ config to your developer sandboxes or deploy new CPQ config to downstream environments. Gearset will automatically handle the population of existing record IDs for any new config at deployment time.
