Introduction

Gearset's CPQ pilot takes a novel approach to deploying CPQ configuration data by treating it just like Salesforce metadata. This has several benefits such as providing an easy way to see differences between your configuration data, deploying it alongside Salesforce metadata, and increasing the likelihood of deployments working first time.

Prerequisites for deploying your CPQ config data

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. For more information on how to run the setup process on your Salesforce orgs, see our CPQ setup walkthrough.

Current pilot limitations for deploying changes

  • The pilot currently supports the deployment of new and changed items only. Support for deploying deleted items will be added as development continues.

  • If you have an Enterprise subscription, you'll be able to roll-back changed items, but not new items.

Comparing and deploying your CPQ config data

Once both your source and target orgs have had the external ID setup process run successfully, you're ready to start comparing your configuration data.

Before starting your comparison, choose the CPQ objects that you wish to include in your comparison via the CPQ tab in the metadata filter dialog. You can also choose to include Billing objects in the comparison.

Comparison results

CPQ config data is displayed in the results grid, just like Salesforce metadata. You can select and deploy both metadata and CPQ config data as part of the same deployment.

CPQ data will be indicated in the metadata type column using the CPQ prefix (e.g. CPQ product, CPQ template, CPQ product options etc.) :

Expanding a CPQ item in the comparison results will display any components or dependencies for that particular item which you can also include in your deployment:

Gearset will automatically handle the population of the record ID for any new item you deploy as part of the final deployment stage process.

The deployment stage of metadata and CPQ

Just like with metadata, any deployment package including CPQ items will also undergo a series of checks to detect common issues that may cause your deployment to fail. These include checking for missing config dependencies and any metadata that also needs to be included for the CPQ deployment to succeed.

The pre-deployment summary will show the full list of CPQ config data being deployed, including any that have been added via the problem analyzers. You can add a name and deployment notes for the deployment which will appear in the metadata deployment history.

Once the deployment process has started, Gearset will deploy any metadata included in the deployment package first. Should this deployment fail, Gearset will follow its current behaviour of stopping the deployment and rolling back any metadata changes meaning your Salesforce org is in its original state. No CPQ deployment will be attempted.

Once the metadata has been deployed successfully, any tests will then run, and assuming all tests pass, your CPQ configuration data will then be deployed.

Note: only changed CPQ items can be rolled back at this time.

From the deployment success page you can see the summary of items deployed with a direct link to each record for easy navigation. The deployment summary will also be added to your deployment history.

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

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

Did this answer your question?