---
schema_version: "1"
id: 32aa0b5ffd71be8fc68a1a602aac889084501e8d715c49820f0802bd5537ff59
title: Omnistudio Data Mapper Best Practices (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_dataraptor_best_practices.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_dataraptor_best_practices.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1555e5e74846a2f3de83ffc332651398d01da823925014a5a5697b221dbbee90
description: For the managed package runtime, to maximize the benefits of Data Mappers, follow the best practices whenever possible.
products:
  - Omnistudio
release: "264"
---
# 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US).

- 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)](https://help.salesforce.com/s/articleView?id=xcloud.os_relationship_notation_versus_multiple_extract_steps.htm&release=264.0.0&type=5 "For the managed package runtime, using relationship notation improves the performance of Omnistudio Data Mappers that retrieve data from a parent of the primary sObject. You use this notation in the Extract JSON Paths for the parent sObject's fields instead of adding a second sObject in the Data Mapper's Extract tab. Two examples illustrate how to use relationship notation.").
- 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](https://developer.salesforce.com/docs/atlas.en-us.salesforce_large_data_volumes_bp.meta/salesforce_large_data_volumes_bp/ldv_deployments_infrastructure_indexes.htm) in Salesforce Help.
- Use caching to store frequently accessed, infrequently updated data. See [Cache for Omnistudio Data Mappers (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_cache_for_dataraptors_and_integration_procedures.htm&release=264.0.0&type=5 "For the managed package runtime, Omnistudio offers multiple caching options to improve performance and minimize unnecessary data processing in Data Mappers. The two primary user-configurable caching types are Org Cache and Session Cache, which are available in the Data Mapper designer. These caching mechanisms are part of the Salesforce Platform Cache and are implemented through Vlocity Cache in Omnistudio with managed package runtime. Each serves a distinct purpose and comes with specific configuration considerations.").

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)](https://help.salesforce.com/s/articleView?id=xcloud.os_dataraptor_or_integration_procedure.htm&release=264.0.0&type=5 "For the managed package runtime, Data Mappers read or write Salesforce SObject data or perform single-step data structure transformations. Integration Procedures can interact with many types of data, including REST APIs and Apex classes, and process it in multiple steps. For some use cases, a single Data Mapper is sufficient. Integration Procedures usually call one or more Data Mappers and are more flexible and powerful. Use these guidelines to help you determine which to build.").