--- schema_version: "1" id: 1afd7c83226901bd18213d903476754bf2564e6d79a48ef7584dc013d42eb898 title: Map Inputs and Outputs for Transformations collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_dataraptor_transform_data_mappings_46630.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_dataraptor_transform_data_mappings_46630.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: c12d49e91140d7b8312fbbbb65ec6fb287222bf9660e718771ba1ea2400d1e29 description: To map data from the input to the output, go to the Transform tab. If you're using the designer on a managed package, go to the Output tab. You can also handle null values, data types, caching, and list transforms. products: - Omnistudio release: "264" --- # Map Inputs and Outputs for Transformations To map data from the input to the output, go to the Transform tab. If you're using the designer on a managed package, go to the Output tab. You can also handle null values, data types, caching, and list transforms. You can map data by using one of these methods: - Use Quick Match to quickly map input and output data in a Data Mapper Transform. See [Use Quick Match to Map Data](https://help.salesforce.com/s/articleView?id=xcloud.os_use_quick_match_to_map_data_46694.htm&release=264.0.0&type=5 "Quick Match is an easy way to map input and output data in an Omnistudio Data Mapper Transform."). - Specify each mapping individually using the Create Mapping option. Both methods apply to JSON input and output and to other input and output types. ## Data Restructuring and Renaming All types of Data Mappers can restructure data and rename fields using mappings. To restructure or rename a field, you map the input path to the desired output path. This example shows JSON input being mapped to XML output. The incoming top-level Case fields, CaseNumber, AccountId, and AccountName, are reparented under an XML element named . Although the list of contacts is unchanged, note the difference between the representation of a list in JSON and in XML. In JSON, the Contacts list is enclosed in square brackets, \[\], then each item in the Contacts list is enclosed in brackets, {}. In XML, each item in the Contacts list is enclosed in a element. For details about converting between JSON and XML, see [XML and JSON in Omnistudio Data Mappers](https://help.salesforce.com/s/articleView?id=xcloud.os_xml_in_dataraptors_46723.htm&release=264.0.0&type=5 "In addition to JSON, Data Mappers can have XML input and output. The XML format in Data Mappers is an unordered key-value, JSON-like structure."). For the PDF, Docusign, and Document Template output types, output mappings are generated based on the fields in the Target Output file you selected when you created the Data Mapper Transform. By default, if a value is null, no node is created for the field in the output JSON. To ensure that a node is created, regardless of whether the field is null, go to the Options tab and select **Include null values in the response**. ## Input Value to Output Value Mappings To verify that your mappings create the desired structure, go to the Preview tab, paste sample input into the Input pane on the left side of the screen, and click Execute. The results are displayed in the Response pane. To verify that your mappings create the desired structure and output, go to the Preview tab, paste the sample input into the Input pane in the correct format, and click **Execute**. The results appear in the Response pane. The Data Mapper Transform generates the desired output only if the input data format is correct. For example, for the Date data type, you must enter the supported format, which is mm/dd/yyyy or yyyy-mm-dd. To define key value pairs for the output, open the mapping, go to Transform Map Values, and enter values in the Key Value pair fields. For example, if the incoming field contains TRUE or FALSE, and your OmniScript requires a Y or N value, enter TRUE or FALSE in the Key field, and Y or N in the Value field, respectively. ## Output Data Types On the Output tab, you can specify the data type of the output data. If you change the type, be sure to choose a compatible output type. (For example, changing a numeric type to a string is fine, but changing a string to a numeric is risky, because a string can contain non-numeric characters.) See [Omnistudio Data Mapper Output Data Types](https://help.salesforce.com/s/articleView?id=xcloud.os_dataraptor_output_data_types_47661.htm&release=264.0.0&type=5 "Many data types can be assigned to data in the Output JSON, including boolean, currency, string, various number and list types, and date formats."). ## Data Caching You can configure optional caching settings on the Options tab: **Time To Live In Minutes**: If data caching is enabled, it determines how long data remains in the cache. The minimum value is 5. **Salesforce Platform Cache Type**: Enables data caching. Set to **Session Cache** for data related to users and their login sessions, or to **Org Cache** for all other types of 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."). ## Maintain List Order When Combining Multiple Inputs When you map multiple input lists to the same output list in a Data Mapper Transform, the system does not guarantee the order of the items in the output. The results may vary between executions. To ensure a predictable and consistent order, use a formula to combine and filter the lists instead of using direct mappings. **Example Scenario** You have three input lists: `inputList1`, `inputList2`, and `inputListNew`. You want to combine them into a single `OutputList` where the items from `inputList1` always appear first, followed by `inputList2`, and then `inputListNew`. **Required Configuration** - Remove direct mappings: Remove any individual mappings that target the `OutputList`. - Add a formula: On the **Formulas** tab, create a formula to merge the lists in your preferred order. | Formula | Formula Result Path | Description | | --- | --- | --- | | `LIST(inputList1, inputList2, inputListNew)` | CombinedList | Merges the lists in the exact order specified. | | `FILTER(LIST(inputList1, inputList2, inputListNew), "PolicyNumber != null")` | OutputList | Merges the lists in order and excludes items with null Policy Numbers. | **Mapping the Result** On the **Transforms** tab, map the result of your formula to the final output path. | Input JSON Path | Output JSON Path | | --- | --- | | OutputList | OutputList | ![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 Make sure that the output data type for your mapping is set to List. - **[Use Quick Match to Map Data](https://help.salesforce.com/s/articleView?id=xcloud.os_use_quick_match_to_map_data_46694.htm&release=264.0.0&type=5)** Quick Match is an easy way to map input and output data in an Omnistudio Data Mapper Transform. - **[Transforming Lists with Data Mappers](https://help.salesforce.com/s/articleView?id=xcloud.os_list_input_for_dataraptors_47431.htm&release=264.0.0&type=5)** Data Mappers can perform list transformations. For mapping input to output, Data Mappers require a list input in which every value is paired with a key.