---
schema_version: "1"
id: 4c161495f2d5c7d52361649dcf5101a8758fd93ee1e0aca9d3899d2762295665
title: Omnistudio Data Mapper Extract Overview (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_extract_overview.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_dataraptor_extract_overview.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e5507ff95b52f640729b8bda9885120d02bb2e99aabafbc1669c8734a624df4d
description: For the managed package runtime, Data Mapper Extracts read Salesforce data and return results in JSON, XML, or custom formats. You can filter the data and select the fields to return. Formulas, attributes, default values, and translations are supported. Extracts typically provide Omniscripts, Integration Procedures, and Cards with the data they require.
products:
  - Omnistudio
release: "264"
---
# Omnistudio Data Mapper Extract Overview (Managed Package)

For the managed package runtime, Data Mapper Extracts read Salesforce data and return results in JSON, XML, or custom formats. You can filter the data and select the fields to return. Formulas, attributes, default values, and translations are supported. Extracts typically provide Omniscripts, Integration Procedures, and Cards with the data they require.

![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).

To define a Data Mapper extract:

1. Create the Data Mapper extract. See [Creating a Data Mapper Extract](https://help.salesforce.com/s/articleView?id=xcloud.os_create_a_dataraptor_extract.htm&release=264.0.0&type=5 "For the managed package runtime, to create a Data Mapper Extract, specify its name, input and output types, and permissions.")
2. Configure the initial extraction. See [Define the Initial Extraction (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_define_the_initial_extraction.htm&release=264.0.0&type=5 "For the managed package runtime, on the Extract tab, you specify the Salesforce objects to be queried and the filters that determine the data to be returned from the object. You can also specify a limit and offset for paging or a field on which to sort.").
3. Determine whether you need multiple extract steps or relationship notation. See [When to Use Multiple Extract Steps (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_when_to_use_multiple_extract_steps.htm&release=264.0.0&type=5 "For the managed package runtime, how many extract steps you need depends on how the object types you are extracting from are related. There are three basic scenarios: single, single with relationship notation, and multiple.") and [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.").
4. (Optional) Add data using formulas. See [Use Formulas in Omnistudio Data Mappers (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_use_formulas_in_dataraptors.htm&release=264.0.0&type=5 "For the managed package runtime, to add data to the output of a Data Mapper, define formulas. Several types of Data Mapper (Extract, Transform, and Load) support formulas. When you define a formula, you map its output to the output JSON (for extracts and transforms) or Salesforce object field (for loads).").
5. Compose the output. See [Defining the Output of an Extract](https://help.salesforce.com/s/articleView?id=xcloud.os_dataraptor_extract_output.htm&release=264.0.0&type=5 "For the managed package runtime, to map data from the extraction step JSON to the output JSON, go to the Output tab. You can also handle null values, attributes, translations, field-level permissions, caching, and list transforms.").
6. Test the Data Mapper. See [Test an Omnistudio Data Mapper Extract (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_test_a_dataraptor_extract.htm&release=264.0.0&type=5 "For the managed package runtime, you can test the input and output of a Data Mapper Extract on the Preview tab.").

- **[Create an Omnistudio Data Mapper Extract (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_create_a_dataraptor_extract.htm&release=264.0.0&type=5)**  
    For the managed package runtime, to create a Data Mapper Extract, specify its name, input and output types, and permissions.
- **[Define the Initial Extraction (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_define_the_initial_extraction.htm&release=264.0.0&type=5)**  
    For the managed package runtime, on the Extract tab, you specify the Salesforce objects to be queried and the filters that determine the data to be returned from the object. You can also specify a limit and offset for paging or a field on which to sort.
- **[When to Use Multiple Extract Steps (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_when_to_use_multiple_extract_steps.htm&release=264.0.0&type=5)**  
    For the managed package runtime, how many extract steps you need depends on how the object types you are extracting from are related. There are three basic scenarios: single, single with relationship notation, and multiple.
- **[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.
- **[Omnistudio Data Mapper Extract Output (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_dataraptor_extract_output.htm&release=264.0.0&type=5)**  
    For the managed package runtime, to map data from the extraction step JSON to the output JSON, go to the Output tab. You can also handle null values, attributes, translations, field-level permissions, caching, and list transforms.
- **[Test an Omnistudio Data Mapper Extract (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_test_a_dataraptor_extract.htm&release=264.0.0&type=5)**  
    For the managed package runtime, you can test the input and output of a Data Mapper Extract on the Preview tab.
- **[Omnistudio Data Mapper Extract Examples (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_dataraptor_extract_examples.htm&release=264.0.0&type=5)**  
    For the managed package runtime, Data Mapper Extract examples demonstrate object relationships, paging with data values, paging with offsets, working with attributes, and relationship notation.