As you build workflows, you will often find that data coming out of one application will need to be reformatted before it is transferred to the destination application.
This is where the Mapper block comes in.
The Mapper block lets you transform data and map fields between two data formats, so that the data coming from one app can be transformed for use in another app.
Please note that both the documentation for the Mapper block and the Mapper block itself are under development. You can expect the Mapper block to gain more features and improve going forward.
The Mapper block is a generic block type, and can be added to any integration project, regardless of apps involved.
To use it, simply drag the Mapper block onto the Canvas and configure the source and target blocks (in the “Working Area” tab):
Click the “Map model” button to begin configuring the mapping table used by the Mapper block.
When the Map Model button is clicked, the Mapper block will ask the source and target blocks to give examples of the data they use, referred to as the model.
The block model can be configured in the block template.
For the input block, the
For most ready-made blocks you will find that the block model is already setup.
The mapper block will use this information to dynamically construct a mapping screen. (You will see a green checkmark appear next to the GetEmployees block as data is pulled, before the mapping screen appears.)
The mapping screen can be thought of as a spreadsheet with two columns – one for the source application, and one for the target application. By connecting corresponding fields, you are building a map for how data should be transformed. And like in a spreadsheet, you also have the possibility to use functions, to concatenate fields, put text to upper case, date manipulation, etc.
Expand the area on the left, and the Target column on the right, as shown in the screenshot.
You can now drag and drop fields from the area on the left into the Source column, to specify how fields will be mapped to the Target column.
But you may notice you are not able to map the zip code field directly, because of a type difference:
The zip code field has a string type in the source model, but a number type in the target model:
To fix this we must change the data type for this field, by clicking the pencil icon.
You are now able to map the Source zip field to the Target zip field.
Save the mappings, and then save the workflow.