---
schema_version: "1"
id: e5e6000882818c6a41187d64529f32fddb0b684dd61b001e95aa62cf362939f9
title: Omnistudio Data Mapper Best Practices
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_47412.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_dataraptor_best_practices_47412.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a1568e74a1b210dacb84b2c5191a011b10a9ca93444ed551582c6b677ac78eb5
description: To maximize the benefits of Data Mappers, follow the best practices whenever possible.
products:
  - Omnistudio
release: "264"
---
# 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](https://help.salesforce.com/s/articleView?id=xcloud.os_relationship_notation_versus_multiple_extract_steps_45995.htm&release=264.0.0&type=5 "Using relationship notation improves the performance of Omnistudio Data Mappers that retrieve data from a parent of the primary object. Use this notation in the Extract JSON Paths for the parent object's fields instead of adding a second object in the Data Mapper's Extract tab.").
- 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](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 [Improving Data Mapper Performance with Caching](https://help.salesforce.com/s/articleView?id=xcloud.os_cache_for_dataraptors_and_integration_procedures_48057.htm&release=264.0.0&type=5 "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 Scale Cache in Omnistudio with standard runtime. Each serves a distinct purpose and comes with specific configuration considerations.").
- 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](https://help.salesforce.com/s/articleView?id=xcloud.os_dataraptor_or_integration_procedure_8166.htm&release=264.0.0&type=5 "Omnistudio Data Mappers read or write Salesforce SObject data or perform single-step data structure transformations. Omnistudio 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.").

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio-264-0-0-production-enus/f526eaa8-ae05-487a-8944-4bb99b0b78ac/images/icon_note.png)

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.