You are here:
Enable Omnistudio Data Mapper Versioning
Manage different versions of your Data Mappers by enabling the Data Mapper Versioning setting. Enabling this feature activates existing standard Data Mappers as version 1 and prevents the editing of active components to ensure consistency. Your implementation automatically uses the active version of a referenced Data Mapper. By default, the Data Mapper Versioning setting is disabled.
Active components aren’t editable. If inconsistencies exist, such as multiple versions already present, an error occurs when enabling Data Mapper Versioning. You must resolve the issues indicated in the error message before enabling Data Mapper Versioning again. If you reference a Data Mapper that has no active version, running the component that executes the Data Mapper returns a “No active version” error.
Before You Begin
To enable Data Mapper versioning, first enable the Omnistudio Metadata setting. This process validates your component naming conventions and fails if any names are invalid. Make sure that the Data Mapper names are alphanumeric and don’t include spaces or special characters (for example, underscores).
- Go to Setup in your org, enter Omnistudio Settings in Quick Find, and select Omnistudio Settings.
- If you haven’t already enabled Omnistudio Metadata API support, turn on the Omnistudio Metadata setting. After this setting is enabled, it can’t be disabled.
- Check your email for confirmation that you've successfully enabled Omnistudio Metadata. If it fails, check that none of your component names have spaces or special characters.
-
Turn on Data Mapper Versioning from the same Omnistudio Settings
page.
You can disable the Data Mapper Versioning setting at any time.
