You are here:
Enable Omnistudio Metadata API Support
To deploy and retrieve Omnistudio standard objects with Salesforce Metadata API, enable the Omnistudio Metadata setting. Until you enable this setting, you can't use Metadata API to deploy Omnistudio components. Future enhancements will depend on this setting and completion of the migration. After this setting is enabled, Omnistudio checks for valid unique names and creates entries for existing components from the standard objects in the Omnistudio configuration tables. Also, for each new component, Omnistudio creates an entry in the Omnistudio configuration tables. Omnistudio Metadata supports OmniProcess (Omniscript and Integration Procedure), OmniDataTransform (Omnistudio Data Mapper), and OmniUiCard (Flexcard) standard objects. This setting doesn't apply to Omnistudio custom objects.
Before You Begin
- Make sure that your org uses the standard object model. See Does Your Org Use Custom or Standard Objects? .
- Make sure that your components have valid unique names.
- When you select the Omnistudio Metadata setting, a process runs that validates your components' names. If one name is invalid, the setting isn’t enabled, and you receive an email.
- The fields used to create uniques must include only alphanumeric characters
and can’t include spaces or special characters such as underscores. After
changing the names, update the references. The fields used to create the unique
names vary by component. For more details, see Omnistudio Naming Conventions.
Component Object Fields That Create Unique Name Integration Procedures OmniProcess Type + Subtype Omnistudio Data Mappers OmniDataTransform Name Omniscripts OmniProcess Type + Subtype + Language Flexcards OmniUiCard Name
- Make sure that the Omnistudio configuration tables don’t contain any records in these
objects:
- OmniUiCardConfig
- OmniScriptConfig
- OmniIntegrationProcConfig
- OmniDataTransformConfig
Any existing records in these objects can prevent the setting from being enabled. Log in to the Developer Console and run a Select query to find any records on the objects.
If there are records in these objects:
- Back up all Omnistudio components (OmniProcess, OmniDataTransform, OmniUiCard) by exporting all the records. For example, in the Omniscripts tab, select Type and click Export.
- After the backup is complete, manually delete all records returned by the SOQL queries for the respective configuration objects.
You can use the backups later to restore standard Omnistudio components if they were removed during the configuration table cleanup process. This scenario is rare.
- If you're migrating from the custom data model to the standard data model, run the Omnistudio Migration Tool and update references. See Migration Process from Omnistudio for Managed Packages to Omnistudio.
After you enable this setting, you can’t disable it.
Required Versions |
|---|
Available beginning Spring '22 and later releases for customers on the standard object model. |
- In Setup, in the Quick Find box, enter Omnistudio Settings and select Omnistudio Settings.
- Enable Omnistudio Metadata.
-
Check your email for confirmation that Omnistudio Metadata is enabled or for
notification of errors.
If there are errors, the Omnistudio Metadata setting initially appears enabled but is then disabled. See Troubleshooting Errors After Enabling Omnistudio Metadata.
-
To allow users other than admins to create, update, or delete Omnistudio
components, enable object permissions in user profiles or permission sets for the
Omnistudio configuration BPOs.
- OmniUiCardConfig
- OmniScriptConfig
- OmniIntegrationProcConfig
- OmniDataTransformConfig
By default, the standard profile has read-only access.

