Inputs and Outputs for Omnistudio Data Mappers

The configuration of inputs and outputs in Salesforce Omnistudio Data Mappers is highly flexible. The primary data formats are JSON and XML with other options available.

JSON is the native and most common format used throughout Omnistudio components. Data Mappers (Extract, Load, Transform) accept JSON payloads passed from Integration Procedures, OmniScripts, or external REST API calls. JSON is also the default and most common format for Extract and Transform Data Mappers, which other Omnistudio components or external REST clients consume.

Use XML for integration with legacy or enterprise systems that rely on XML-based messaging. Load and Transform Data Mappers can accept XML payloads, which is useful for handling responses from callouts made within an Integration Procedure. If you use XML output for Extract and Transform Data Mappers, Omnistudio can send data to external XML-dependent systems.

For highly non-standard data structures that JSON or XML can’t handle, Data Mappers offer custom input (for Load and Transform) and output (for Extract and Transform) as an option through Apex.

Finally, because a Data Mapper Transform’s purpose is to manipulate data, it can convert data into formats for document generation. A Transform converts structured JSON into the format to create a PDF. Transforms also structure data to populate fields in a DocuSign envelope or another document template.

• Omnistudio Data Mapper Output Data Types
  Many data types can be assigned to data in the Output JSON, including boolean, currency, string, various number and list types, and date formats.
• XML and JSON in Omnistudio Data Mappers
  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.
• Custom Input and Output for Omnistudio Data Mappers in Omnistudio
  By default, Data Mappers handle JSON and XML data. To handle other data formats, you can configure a Data Mapper to use a custom input or output that you implement is a custom class. For example, you can define a Data Mapper Transform that accepts CSV-formatted data and outputs it as JSON.