When aligning your Salesforce orgs for deploying CPQ configuration we recommend as a preferred solution to perform a full copy sandbox refresh after the Gearset external ID setup wizard has been run on your Production org. It's the cleanest way in which to ensure your orgs are perfectly in sync. However, it may not always be possible if your Production and Full Copy Sandbox orgs are very out of sync or refreshes occur infrequently. In this case, an alternative solution is to manually sync your CPQ configuration using Gearset’s new CPQ features between any of your orgs.
Note: To make the process simpler, you should complete any CPQ development in your dev orgs and migrate them to either your full copy sandbox or production org.
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 2: Manually sync your Production and Full copy sandbox orgs
Whilst we recommend aligning your orgs via the full copy sandbox refresh solution approach, the steps below provide a top level guide on how you can also manually sync existing CPQ config between two orgs that have the same Salesforce record ID (i.e. between your full copy sandbox and production org). See our comparing and deploying CPQ configuration user guide for a more detailed guide on how to perform those actions within the Gearset UI.
Step 1: Run the Gearset external ID setup wizard on both your production org and full copy sandbox org
Note: this step is required for both orgs and you can read our documentation on how to run the setup wizard for your Salesforce org connections via our documentation.
Gearset will first perform a metadata deployment to add its external ID field to CPQ and related standard CPQ objects. A data deployment will then take place to populate the external ID field with an ID that's derived from the existing Salesforce record ID.
As the full copy sandbox and production orgs already share the same record IDs, Gearset's derived record IDs enable it to compare the CPQ configuration between the two orgs to find records that exist in both that are either changed or unchanged, only exist in the source but not the target, or only exist in the target but not the source.
Step 2: Compare your Salesforce metadata and CPQ configuration to identify the differences
Once the external ID setup has been completed on both orgs, you can choose the metadata and CPQ objects that you want to include in your comparison.
Step 3: Select the Salesforce metadata and CPQ configuration that you want to sync
There will often be dependencies between metadata and your CPQ config, so you need to include both in your deployment to increase the chances of it working first time.
Step 4: Deploy your chosen metadata and CPQ configuration to your Production org
Gearset will deploy your metadata, followed by the CPQ configuration so that your orgs both contain the information that you need.
Gearset will automatically populate the new record ID(s) as the configuration changes are deployed between your environments.
Note: If you have changes in a sandbox that you also want to deploy, you can also manually run the external ID setup on it and deploy the remainder of your CPQ configuration after your full copy sandbox and production org are in sync.