Please note that the functionality described in this document is part of the Gearset Revenue Cloud Advanced pilot program.
To inquire about gaining access to this pilot and explore how it can benefit your team, please reach out to our dedicated support team. We will be happy to provide you with more information and guide you through the access process.
Introduction
Gearset's Revenue Cloud Advanced (RCA) deployment solution handles Revenue Cloud Advanced configuration just like standard Salesforce metadata. This offers several advantages, such as easily identifying differences in your Revenue Cloud Advanced setup, deploying it alongside your other Salesforce metadata, and improving the success rate of your deployments.
To compare and deploy any Revenue Cloud Advanced configuration using Gearset, both the source and target org Revenue Cloud Advanced components and related objects need the Gearset external ID field. Our convenient 1-click external ID setup feature automates the process of adding this field for you.
Running the Gearset external ID setup on your Salesforce orgs
Ensure the Gearset external ID setup has been run on both orgs.
To start, go to your Salesforce connections page. For each org involved in Revenue Cloud comparison and deployment, select the Run external ID Setup option and complete the steps.
For details, see our external ID setup walkthrough here.
Configuring your Revenue Cloud comparison requirements
The next step is to correctly configure and choose the Revenue Cloud objects and related metadata that you wish to include in your comparison, using the comparison filter dialog.
The Gearset Revenue Cloud configuration is preconfigured to include recommended core metadata and Revenue Cloud objects which you can further configure and save as your own filter if you prefer. We have added support for Product Catalog Management first, which is why this filter is labelled "PCM configuration".
To correctly configure your filter for Revenue Cloud Advanced comparisons and deployments, you should include the following in the filter dialog:
The Revenue Cloud Advanced objects you wish to include, via the
Revenue Cloudsection.Any related Salesforce metadata upon which your RCA configuration also has a dependency. These would typically include, though not be limited to,
Custom object,Flow,Approval Process,Permission SetsandProfile, via the metadata tab.
Note: Deployment failures can result from not having configured your comparison correctly to include metadata which your Revenue Cloud config has a dependency upon.
Comparison results and deploying your Product Catalog Management (PCM) configuration
PCM configuration data appears in the results grid, similar to Salesforce metadata. You have the flexibility to select and deploy both metadata and Revenue Cloud configuration data within a single deployment.
PCM data will be identified in the metadata type column using the "PCM" prefix (e.g., PCM product, PCM product selling model, PCM product catalog, etc.):
Note: Expanding an item in the comparison results will display any components or dependencies for that particular item that you can also include in your deployment.
The deployment stage of metadata and PCM
To proceed with the deployment, select the items on the comparison screen, then click on the NEXT button:
At this stage Gearset will perform a series of checks to detect common issues that might cause your deployment to fail. If it's all good then you'll find a screen like this one
But if there are problems that need to be fixed then you'll see it here:
In this case, for example, we've found that an addition of missing components will increase the likelihood of deployment success.
Here you can review and tick the suggestions to fix the problem. Once ready click on the Pre-deployment summary button on the bottom right end corner.
The pre-deployment summary will show you the full list of Revenue Cloud records and associated metadata being deployed, including any that have been added through the problem analyzers.
You can add a friendly name and deployment notes for the deployment, which will show up in the metadata deployment history for future reference.
The options from here are to either validate the package, schedule the deployment or deploy it now.
Once the deployment begins, Gearset will initially deploy any metadata included in the deployment package.
If this metadata deployment fails, Gearset will maintain its standard behavior of halting the process and rolling back the metadata changes, ensuring your Salesforce org remains in its initial state. In this scenario, no Revenue Cloud deployment will be attempted.
Upon successful metadata deployment and the passing of all tests, your Revenue Cloud configuration data will then be deployed.
Note: Currently, only modified Revenue Cloud items can be rolled back.
From the deployment success page, you can see the summary of items deployed, which will also be added to your deployment history.
By clicking on the Deployed config data items tab, you can view a list of all the Revenue Cloud config data items that have been deployed, with a direct link to each record for easy navigation.
And that's it! Congratulations on successfully deploying your Revenue Cloud configuration data to your target org!