Mapper 2.0 examples

The following examples demonstrate how Mapper 2.0 handles record and row formatting between exports and imports.

• Example 1: Record-to-record mapping
• Example 2: Record-to-row mapping
• Example 3: Row-to-record mapping

Example 1: Record-to-record mapping

This example builds a destination app JSON record structure out of fields available in the source application’s JSON record structure data. This is a record-to-record mapping, meaning that the JSON structures for both input and output begin and end with curly braces {}.

Tip: When setting up your mapping configuration for data sent from your source app to your destination app, you should review the API documentation for your destination app to find the JSON structure required by the destination endpoint. 

The source application JSON data displays in the Input window in the upper right corner of the Mapper 2.0 interface. 

Enter each Destination field name in the left column, select its data type, and use the Source field drop-down list from the right column to select the field from your source data that will populate the import data. The data type you select determines the structure and field formatting displayed in the Output window when you click Preview. You can drag and drop lines to rearrange the order of fields, but you can't drag and drop a field to another level of the JSON hierarchy. 

The above configuration creates the following output record displayed in the Output window in the lower right corner of the Mapper 2.0 interface. 

Click Preview to update the JSON data based on your most recent configuration, or check Auto-preview to automatically update the output with each change you make. 

Example 2: Record-to-row mapping

This example builds a destination app JSON row structure out of fields available in the source application’s JSON record structure data. This is a record-to-row mapping, meaning that the input JSON structures begin and end with curly braces {}, and the output JSON structures begin and end with brackets [].

Tip: When setting up your mapping configuration for data sent from your source app to your destination app, you should review the API documentation for your destination app to find the JSON structure required by the destination endpoint. 

The source application JSON data displays in the Input window in the upper right corner of the Mapper 2.0 interface. 

Enter each Destination field name in the left column, select its data type, and use the Source field drop-down list from the right column to select the field from your source data that will populate the import data. The data type you select determines the structure and field formatting displayed in the Output window when you click Preview. You can drag and drop lines to rearrange the order of fields, but you can't drag and drop a field to another level of the JSON hierarchy. 

The above configuration creates the following output record displayed in the Output window in the lower right corner of the Mapper 2.0 interface.  

Click Preview to update the JSON data based on your most recent configuration, or check Auto-preview to automatically update the output with each change you make. 

Example 3: Row-to-record mapping

This example builds a destination app JSON record structure out of fields available in the source application’s JSON row structure data. This is a row-to-record mapping, meaning that the input JSON structures begin and end with brackets [], and the output JSON structures begin and end with curly braces {}.

Tip: When setting up your mapping configuration for data sent from your source app to your destination app, you should review the API documentation for your destination app to find the JSON structure required by the destination endpoint. 

The source application JSON data displays in the Input window in the upper right corner of the Mapper 2.0 interface. 

Enter each Destination field name in the left column, select its data type, and use the Source field drop-down list from the right column to select the field from your source data that will populate the import data. The data type you select determines the structure and field formatting displayed in the Output window when you click Preview. You can drag and drop lines to rearrange the order of fields, but you can't drag and drop a field to another level of the JSON hierarchy. 

The above configuration creates the following output record displayed in the Output window in the lower right corner of the Mapper 2.0 interface.

Click Preview to update the JSON data based on your most recent configuration, or check Auto-preview to automatically update the output with each change you make.