Omnistudio Data Mapper Best Practices (Managed Package)

For the managed package runtime, to maximize the benefits of Data Mappers, follow the best practices whenever possible.

Managed Package app icon This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

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 (Managed Package).
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 Cache for Omnistudio Data Mappers (Managed Package).

To determine whether a Data Mapper or an Integration Procedure is best for your use case, see Omnistudio Data Mapper or Integration Procedure? (Managed Package).