💡 A note on terminology: In this article, Revenue Cloud refers to both Salesforce CPQ and Agentforce Revenue Management (formerly RCA).
Keeping your data unique
If you’re using Gearset to deploy Revenue Cloud configuration data, your first step is to run our External ID wizard.
When you clone a record in Salesforce, you may accidentally clone its unique Gearset External ID too. To prevent this, Gearset uses simple, purpose-built flows to ensure every record keeps a truly unique External ID. This keeps your deployments clean and error-free.
When you run the External ID wizard, Gearset will ask how you’d like to handle these de-duplication flows. You’ll see these options on the second-to-last screen of the wizard.
You’ll see exactly which objects are affected on the second-to-last screen of the wizard.
If you change your mind about the de-duplication flows they are straightforward to roll back, as are the External IDs themselves.
This is an example of the flow that will be created to keep the IDs on Product records unique.
Option 1: On all supported objects
This is our most popular choice because it offers the broadest protection.
It adds a flow to every object Gearset supports, ensuring that whenever a record is cloned, the External ID field is cleared. This allows Gearset to generate a fresh, unique ID the next time you deploy.
Many teams find that this is the best option for them as it accounts for all objects within the scope of Revenue Cloud, not just those with the CloneWithRelated option.
Option 2: On all objects with CloneWithRelated in layouts
Choosing only to create flows for objects with CloneWithRelated in their layouts will create a smaller number of flows and therefore less coverage for preventing the duplication of the Gearset External IDs.
What is CloneWithRelated?
The "Clone with Related" button in Salesforce is a great time-saver for iterating on complex configurations.
This clones the records visible directly in Salesforce, you can't clone information that your user doesn't have permission to view and access.
Option 3: Do not add flows
If you choose this, Gearset won't create any flows. You’ll need to manage duplicate External IDs manually. We generally don't recommend this unless you have a specific custom process in place, as it’s much harder to fix duplicate IDs later on.
Top Tip: If you change your mind later, don't worry! These flows (and the External IDs themselves) are very easy to roll back.
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!