Omnistudio Data Mapper Best Practices

To maximize the benefits of Data Mappers, follow the best practices whenever possible.

• Use unique names for Omniscript elements and Data Mapper response nodes.
• Create targeted Data Mappers that only extract or load the data needed for one operation.
• Use relationship notation (queries) whenever possible to pull data from other SObjects. For more information, see Relationship Notation versus Multiple Extract Steps.

• To ensure data security and maintain compliance with Salesforce encryption access controls, always check that a user has the View Encrypted Data permission before displaying or processing decrypted values of encrypted fields.

• To avoid performance issues on the server, keep the number of SObjects to three or fewer.
• Ensure that all filtering and sorting (ORDER BY) operations are on indexed fields. The Id and Name fields are always indexed. For more information, see Indexes in Salesforce Help.
• Use caching to store frequently accessed, infrequently updated data. See Improving Data Mapper Performance with Caching.
• In a Data Mapper Extract, when you use the Equals filter (=) with a null value, the filtering doesn't function correctly due to a known limitation. To prevent this issue, add an additional Not Equal To (!=) filter. For example, to filter for null account values that have a phone number associated with them, use accountId = null AND phone != null.

To determine whether a Data Mapper or an Integration Procedure is best for your use case, see When to Use Omnistudio Data Mappers and Integration Procedures.

Note From version 240 to 242.7, Data Mapper versioning is available in Omnistudio, in Setup, under Omnistudio Settings. With version 242.8, Data Mapper versioning isn't available. Data Mapper versioning isn't recommended, but if you enable it, it does work. If you want to disable it, make sure every Data Mapper in your org has only one version, then contact Salesforce support.