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 via the in-app chat. We will be happy to provide you with more information and guide you through the access process.
To deploy Revenue Cloud changes, the Gearset External ID must be present in both your source and target orgs.
Running the Gearset external ID setup wizard
You can manually instigate running the setup process via your Salesforce org connections page using the Run external ID setup option for any of your Revenue Cloud org(s).
The Revenue cloud external ID setup process
Once you've chosen an org to run the external ID 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 external ID setup.
Simply click the Create Gearset external IDs button to begin the automatic three-step process, and you're done!
💡 Make sure to select the option Do not add flows.
Gearset's automatic 3-step external ID setup 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 Gearset 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 from the existing Salesforce record ID.
The deployment success page will confirm the Gearset external ID field has been added successfully.
💡 When it comes to deploying new records that have been created after this setup step has finished - Gearset will automatically populate new record IDs at the point of deployment alongside any selected metadata.
For any orgs that you've added the Gearset external ID field to, you will be able to run a comparison and select Revenue Cloud items for deployment. See our comparing and deploying Revenue cloud (link later) config article for more information.