Global Unique ID Setup
The establishment of a Global Unique ID (GUID) column on all objects during day-one initialization is a recommended practice for Salesforce DevOps.
Salesforce uses its own internal ID for records, but this ID isn’t portable. The same record in a testing, sandbox, or production org has different Salesforce IDs. This makes tracking a single piece of data across environments nearly impossible. By introducing your own custom, externally set GUID, you have a single, immutable, and universally consistent identifier.
You can also choose your preferred method to maintain the mapping of records IDs across orgs.
Before performing any deployment work, establish your GUID across all database objects, and across all Salesforce orgs involved in your deployment plan.
Add a GUID field to all objects used during your deployment. Since you can’t add fields to metadata types (such as a Flow), use the API name for each metadata type as the unique identifier.
-
Add a GUID field to all objects used during your deployment to ensure unique identification of records across environments.
-
The format and values of the Global Unique ID (GUID) are up to you. Here’s some guidance on what makes a good versus poor GUID for deployment tracking.