Note: The new CPQ features are currently part of a closed pilot so functionality is subject to change at any time without notice.

In order to deploy your CPQ changes between your chosen source and target, the first step is to run Gearset's external ID setup process on both orgs.

Adding Gearset's external ID field offers several benefits:

  • Adding the external ID is a simple, automated operation requiring no complex configuration

  • It helps prevent duplicate records from being created

  • It enables Gearset to easily identify the type of changes that need to be deployed

  • The external ID doesn't interfere with any existing CPQ external ID fields you might already have

  • It can be easily rolled back through Gearset's deployment roll-back feature

You are only required to run the setup process once per Salesforce org.

Running the CPQ setup

You can enter the setup process for any of your CPQ enabled orgs via two pathways.

Path 1: When selecting an org

The first is when configuring a comparison, a check is performed and if the external ID setup process for your org hasn't been performed previously you'll be offered the chance to run the setup process:

Path 2: Via the connections page

Alternatively, you can manually instigate running the setup process via your Salesforce org connections page using the Run CPQ external ID setup option for any of your CPQ org(s).

The CPQ external ID setup process

Before starting the setup process you can give the deployment a name and it'll be stored as an entry in your metadata deployment history with the source metadata location being displayed as CPQ external ID setup.

Simply click the Create Gearset external IDs button for your selected org to begin the automatic three step process.

Step 1: Several checks on the org to make sure Gearset's external ID field can be added are carried out.

Step 2: A metadata deployment is performed to add the external ID field to your CPQ and related objects.

Step 3: Gearset will then populate those external ID fields that were added in step 2. Gearset will derive its external ID value from the existing Salesforce record ID.

The deployment success page will confirm it has successfully added the Gearset external ID field.

Once the setup process on each org you want to compare and deploy CPQ config data changes to has been completed, you'll then be able to run a comparison and select CPQ items for deployment. See our comparing and deploying CPQ config article for more information.

You'll have to also select to include CPQ config data via the metadata filter before starting your comparison.

If you'd like to be added to the CPQ pilot list then contact us via the in-app chat to register your interest.

Did this answer your question?