💡 A note on terminology: In this article, Revenue Cloud refers to Agentforce Revenue Management (formerly Revenue Cloud Advanced aka RCA) and Salesforce CPQ.
How does Gearset deploy Revenue Cloud configuration data?
Gearset bridges the gap between data and metadata by treating Revenue Cloud configuration data as individually deployable components, compared and deployed alongside metadata components. This unified approach provides critical advantages like:
Dependency Mapping: Gearset automatically identifies and maps relationships between records and the metadata they rely on. By understanding these relationships, Gearset can combine data and metadata into a single deployment package, ensuring the target org remains functionally consistent.
Precise Deployments: Gearset allows the user to select specific combinations of configuration, such as specific Products and their related Price Book Entries.
Deployment Sequencing: Gearset automatically determines the correct order of operations, preventing deployment failures caused by missing parent records or related metadata.
In this example you can see a comparison where Gearset has mapped the relationship between Product records, and the custom object changes that affect them. All of these changes will be deployed together, and Gearset will sequence the deployment to ensure success.
Prerequisites - the External ID wizard
Before you can run your first deployment, you will first need to run Gearsets External ID wizard on at least your source and target orgs.
To deploy Revenue Cloud configuration data (like Price Book Entries, Products, and Rules) just as easily as you deploy metadata, Gearset needs a way to track those records across different environments.
In Salesforce, a record’s "Salesforce ID" changes whenever it moves to a new org. Without a consistent ID Gearset wouldn't know that "Product A" in your Sandbox is the same as "Product A" in Production.
The unique Gearset External ID that Gearset adds to all of your Revenue Cloud data (and keeps unique, using de-duplication flows) let's us recognise the same record as it moves between your orgs, and the Salesforce Record ID changes.
Learn more about running the wizard, aligning your IDs and our FAQs.
Step 1 - Configure your comparison
On this page choose your source and target environment. You can run a comparison between them immediately, or choose a comparison filter.
As with a typical metadata only comparison, you will be able to specify which components you want Gearset to retrieve for your comparison.
Gearset provides some default filters to help you find the components you need. Not to be confused with a "data template" these filters include both metadata and configuration data, to help you find what you need for your deployments.
Out of the box Gearset provides filters for:
Salesforce CPQ
Agentforce Revenue Management (formerly Revenue Cloud Advanced aka RCA)
All of these filters can be further customised, by broadening or narrowing their scope, using SOQL queries or specifying named items.
When you are ready to begin your comparison, click "Compare now".
Step 2 - Select your components for deployment
Revenue Cloud configuration data appears in the results grid, in the same way as your Salesforce metadata. You can deploy Revenue Cloud configuration data alongside your metadata.
Identification: Look for your components in the way that is easiest for you - you can navigate the comparison by component name, type etc.
Dependencies and related records: Expand any item to see related components that should be included in your deployment. Gearset will track dependencies from configuration data to metadata, and from data to other data.
Results not what you were expecting? Check if you need to align your IDs.
After you have selected your components, click "Next". Gearset will assess your deployment for any issues, and suggest automatic fixes that you can apply.
In this example, we've found that adding dependent records will allow the deployment to succeed.
Here you can review and tick the suggestions to fix the problem. Click "Pre-deployment summary".
This page shows the components to be deployed to your target. Add a deployment "friendly name" and the associated ticket from your change management platform here.
You can schedule the deployment or click "Deploy now".
Step 4 - Sequencing the deployment automatically
If your deployment contains both configuration data and metadata these components need to be deployed in a specific order, which Gearset takes care of by automated sequencing.
This vastly reduces the complexity of planning and making Revenue Cloud deployments, allowing complex packages of interdependent changes to be deployed in a single click, improving change visibility and velocity.
Once the deployment begins, Gearset will first deploy any metadata included in the deployment package.
If this metadata deployment fails validation, the deployment will stop and the org will automatically be rolled back to its previous state. Gearset will not attempt to deploy the configuration data.
If the metadata deploys successfully Gearset wll immediately trigger the data deployment.
As the data deployment begins Gearset automatically plans the steps to make sure that the records are deployed in the correct order (for example making sure a ProductClassification record is deployed before the Product that depends on it).
If any of the records fail to deploy successfully Gearset will skip them and try the following record, and present the error message along with a suggested resolution on the results page.
The deployment of these records can be retried from the results page after any suggested resolutions are applied.
Reviewing your results
You will be able to view your successfully deployed records on the target org using the "View on target" link in the results.
All historical Revenue Cloud deployments made by your team will be recorded on this page.
A note on rolling back Revenue Cloud deployments
It is straightforward to rollback metadata deployed through Gearset, using these steps.
You can roll back any configuration data changed by Gearset as part of your deployment, but Gearset does not currently support rolling back new records (i.e. records that were "new" when you deployed them). This is because to "roll back" these records would involve mass deleting the data from your org, which at present is not a permission Gearset asks of our users.
Call for feedback
We're always eager to hear user feedback, and to understand how we can best support your team. Please get in touch over the in-app chat if you have any questions or feedback for us!