Create an Omnistudio Data Mapper Load (Managed Package)

For the managed package runtime, to create a Data Mapper Load, specify its name, input and output types, permissions, and options.

1. Go to the Data Mapper Designer tab.
2. Click New.
3. On the Create dialog, specify the following settings, and click Save:

   • Data Mapper Interface Name — Descriptive name of your choice

   • Batch Size — Number of records processed per batch transaction, between 1 and 2000

   • Interface Type — Load

   • Input Type — Choose JSON, XML SObject, or Custom. If your Data Mapper load is called from an Omniscript, choose JSON. If you choose sObject, select the interface object for the input data from the dropdown list. (More information: Interface Objects for External Data Loads (Managed Package). For details about custom data serialization, see Custom Input and Output for Omnistudio Data Mappers in Omnistudio for Managed Packages (Managed Package).)

     

     Note

     SObject input isn't supported in Summer '21 and later releases.

   • Output Type — SObject

   • Required Permission — If specified, this setting limits who can run this Integration Procedure. Specify a comma-separated list of custom permission names.

4. On the Objects tab, specify the Salesforce objects that you want to update.
   The FeedComment and IdeaComment objects aren't selectable.
5. On the Formulas tab, define any transformations you want to apply to the input data to add data to the output data. For details about the functions that you can use in formulas to define transformations, see Use Formulas in Omnistudio Data Mappers (Managed Package).
6. On the Fields tab, map the input data to the Salesforce object fields that you want to update. For more information, see Object Field Mapping (Managed Package).
7. On the Options tab are optional properties you can set.

   The following options are available only if the Input Type is SObject:

   • Batch Size — The number of records processed per batch transaction, between 1 and 2000.

   • Process Now Threshold — The number of records processed immediately, between 0 and 199.

   • Preprocessor Class Name — The adapter Apex class that implements the IDRPreprocess Apex interface.

   • Delete on Success — Automatically delete bulk records after successfully bulk-loading data.

   • Process Super Bulk — Process large jobs spread over multiple Salesforce Apex batch jobs without exceeding Salesforce governor limits.

   • Is Default for Interface — Specify this Data Mapper as the default bundle for the specified interface object.

   The following options are available for all Data Mapper Loads:

   • Ignore Errors — Execute the Data Mapper even if errors occur, skipping only the steps having errors. This option is useful when you know a record will fail with limited data and future steps don't rely on previous steps.

   • Rollback on Error — Don't create or update the sObjects if errors occur. For more information, see Apex Transactions and Transaction Control in the Salesforce documentation.

   • Use Assignment Rules — Use assignment rules for sObjects such as Cases that have user assignment fields. For more information, see Set Up Assignment Rules in the Salesforce documentation.

     In Summer '19 and later releases, if emails are configured in Case assignment rules, checking this option automatically sends emails to users when Cases are assigned.

   • Overwrite Target For All Null Inputs — If an input doesn't have a value, set the corresponding output value to NULL.