We've made deploying CPQ configuration a much simpler task by now treating it in the same way we treat Salesforce metadata.

Before comparing and deploying your CPQ configuration, your Salesforce source and target orgs must have the Gearset external ID field. We've created a new setup wizard to take care of this for you. The only other question is how you want to set up your orgs to contain the Gearset external ID before you begin comparing and deploying your own CPQ configuration.

Adding the Gearset external ID using the new setup wizard

In order to compare and deploy CPQ changes between your chosen source and target, the Gearset external ID field must exist on both orgs. It's a simple 1-click process to run Gearset's external ID setup process using our new CPQ setup wizard.

Setting up your orgs correctly for CPQ deployments in conjunction with the Gearset external ID setup wizard

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. There are two main approaches to this:

The full copy sandbox refresh approach: The cleanest and recommended way to make sure your full copy sandbox and production org CPQ configuration is perfectly in sync is via a full copy sandbox refresh.

The manual sync approach: 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.

Comparing and deploying your CPQ configuration

Once you're happy with the chosen approach to making changes between your source and target(s), and the Gearset external ID field exists in both orgs, you're ready to start comparing and deploying your CPQ configuration - just like metadata! See our CPQ compare and deploy walkthrough for more information.

Did this answer your question?