Loading

Troubleshooting the error "No bundle is specified" in OmniStudio DataMappers

Fecha de publicación: Nov 19, 2024
Descripción

1. Insufficient User Permissions

This error can occur if the user executing the DataMapper does not have the appropriate permissions to access it. To prevent this:

  • Ensure the user has the required object-level permissions such as Read access to the DataMapper object.
  • Confirm the user also has the correct record-level access to the specific DataMapper being used.

Without sufficient access, the DataMapper may fail validation during execution and trigger this error.

2. DataMapper Versioning Enabled (Deprecated Behaviour)

The error may also appear if DataMapper Versioning was enabled previously under OmniStudio Settings.
With versioning activated, a DataMappers must be explicitly activated before it can be executed.

  • Important: The DataMapper Versioning setting has been deprecated by Salesforce and is no longer available in OmniStudio Settings.
  • However, older orgs or configurations that previously used this setting may still have inactive DataMappers requiring manual activation to work properly.


Note: Please refer to the following Salesforce Help Documentation regarding OmniStudio Settings: OmniStudio Settings.

Solución

Step 1: Verify and Fix User Permissions

Ensure the user executing the DataMapper has the following:

  • Object Permissions: At least Read access to the DataMapper object.
  • Record-Level Access: Access to the specific DataMapper record.

For OmniStudio Standard, DataMappers are stored in the OmniDataTransform sObject. For legacy Vlocity(vlocity_cmt/vlocity/ins) custom data model orgs, DataMappers are stored under namespace__DRBundle__c sObject. Providing object and record level access to this should resolve the issue in most case. 

Step 2: Reactivate DataMapper (Only If DataMapper Versioning is Enabled)

If DataMapper Versioning is still affecting execution, follow these steps to activate the affected component:

  1. Go to Setup, then open Developer Console.
  2. Run the following SOQL query:
    SELECT Id, Name, IsActive FROM OmniDataTransform
  3. Identify the affected Data Mapper by Name.
  4. Check the IsActive column
  5. If IsActive = False, it must be activated.
  6. Double-click the value, enable the checkbox, and click Save Rows.
  7. Retry executing or previewing the Data Mapper.

Step 3 (Optional / Not Recommended): Add Rollback Configurations

⚠ This is not recommended for Production, as it may cause unexpected behaviour in execution of Integration Procedures or Data Mappers in Standard Runtime.

If required as a temporary workaround, add the below configuration. Please note that this setting would affect all the DataMappers and Integration Procedures across the org and is not recommended to be used in Production. 

  1. Go to Setup
  2. Search for Omni Interaction Configuration
  3. Click New Omni Interaction Configuration
  4. Add the following:
LabelNameValue
RollbackDRChangesRollbackDRChangestrue
RollbackIPChangesRollbackIPChangestrue

Número del artículo de conocimiento

000393976

 
Cargando
Salesforce Help | Article