For the managed package runtime, Data Mappers have additional caching, security, batch, and debug settings. You can also export and deploy Data Mappers.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
Metadata and Data Caching
Data Mapper metadata is cached for better performance if you allocate space in the VlocityMetadata cache partition. You can configure data caching on the Options tab of Data Mapper Extracts, Turbo Extracts, and Transforms. Data Mapper data is cached if an Integration Procedure that uses caching invokes it. See Cache for Omnistudio Data Mappers (Managed Package).
Data Mapper Security
Security settings control a user's ability to run Data Mappers and cache data. See Security for Omnistudio Data Mappers and Integration Procedures (Managed Package).
Access Data Mapper Configuration Settings
To configure a Data Mapper to run in batch mode in Salesforce Classic:
Data Mapper Batch, Apex, and Debug Settings
Configuration settings are as follows:
-
Batch Size: The number of records processed per batch transaction.
-
Process Now Threshold: Number of records processed immediately (between 0-199).
ImportantTo configure a Data Mapper to run in batch mode, set the Process Now Threshold value to -1.
-
Preprocessor Class Name: Adapter Apex class that implements the IDRPreprocess Apex interface. Used for transforming data before it’s inserted into an Interface Object.
-
Delete on Success: Deletes the Interface Object records on success (meaning that all steps executed without throwing errors). To make troubleshooting easier, disable while debugging.
-
Process Super Bulk: Use batch Apex for processing. Prevents exceeding Salesforce governor limits for complex Interface Objects.
-
Ignore Errors: Ignores all errors during processing.
DataPacks for Export and Deployment of Data Mappers
To copy Data Mappers from one org to another, you export them as data packs, which can then be deployed. To import or export a Data Mapper, go to the Data Mapper tab and choose Import in the tab header or Export in the Data Mapper's dropdown.
When you export a Data Mapper, Omnistudio creates a data pack (which is a JSON file) in your browser's download directory. To deploy the exported Data Mapper to the target org, copy the file to an accessible location and import it. After you import a Data Mapper, you must activate it to be able to run it.