Troubleshooting Errors After Enabling Omnistudio Metadata

Invalid Component Names

For successful migration, the names, types, and subtypes of all Omnistudio components must not have underscores, spaces, or special characters. 

• Omniscripts (OmniProcess object)
• Flexcards (OmniUiCard object)
• Data Mappers (OmniDataTransform object)
• Integration Procedures (OmniProcess object)

Data Mapper Version Numbers

Data Mappers don't have version numbers. Open the Data Mappers and ensure they don't have a version number ("1"). If they don't, they aren’t versioned. You can run the following anonymous Apex in the Developer Console to correct this issue.

List<OmniDataTransform> allDrsToUpdate = new List<OmniDataTransform>();
for (OmniDataTransform om : [ Select Name, VersionNumber from OmniDataTransform WHERE UniqueName = null ]) {
if (om.VersionNumber == null) {
om.VersionNumber = 1;
}
allDrsToUpdate.add(om);
}
update allDrsToUpdate;

Populated Config Tables

To check whether the configuration tables are populated, run a SOQL query in the Developer Console on 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.

• 1. Back up all Omnistudio components (OmniProcess, OmniDataTransform, OmniUiCard) by exporting all the records. For example, in the Omniscripts tab, select Type and click Export.
  2. 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.

Deactivate Omniscripts and Flexcards

Deactivate Flexcards and Omniscripts, and then enable the Omnistudio Metadata setting.