Note: We'll use the term Revenue Cloud in the following article to refer to both Salesforce CPQ and Agentforce Revenue Management (formerly Revenue Cloud Advanced) configuration data.

If you're using our solution for Revenue Cloud, which allows you to compare and deploy configuration data in the same way as metadata, you must first run the External ID wizard . We don't want the act of cloning a record to also clone the unique value that Gearset has populated the External ID with, so Gearset will use purpose made flows to make sure that these values are kept unique.

When you run the External ID wizard to set up your org for Revenue Cloud deployments, Gearset will present you with three options:

Depending on which one you choose, Gearset will create or not create the de-duplication flows on your org. You will see which objects the flows will be created for on the penultimate screen of the External ID wizard.

If you change your mind about the de-duplication flows they are straightforward to roll back, as are the External IDs themselves.

This will add a de-duplication flow to all of the objects that can support it, an example of one of these flows is below.

The flow will make sure that when a record is cloned, the Gearset External ID field is blank. This allows Gearset to create a new, unique External ID at the point that record is deployed.

"On all supported objects" is the broadest option, and will give you the most coverage. 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.

The “Clone with related” feature found on some of the layouts in Salesforce Revenue Cloud makes it easy to create new configuration based on existing Revenue Cloud records and their related objects. This is very handy for many users as it saves them a lot of time when creating similar Revenue Cloud configuration and iterating on their work.

This clones the records visible directly in Salesforce, you can't clone information that your user doesn't have permission to view and access.

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.

If you choose this option no flows will be created on your org, and you will need to manage the issue of duplicate External IDs manually or through another method. We do not recommend choosing this option unless you have a clear plan to manage any possible duplicate IDs, as if you change your mind later the flows will not retroactively manage any duplicate IDs that have been created.

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!