In Integrator, it is possible to map
source fields to
destination fields, exclude fields, add fields to the
destination which do not exist in the
source, and more.
The integrator can automatically read field names from the source and destination objects. It then populates the SOURCE and DESTINATION drop-downs. Manually enter the field name if it is not available in the drop-down.
It is also possible to define a template for the source or destination, so that Integrator won't have to connect to the actual data source.
If a field name is not available in the drop-down, click the
Clear Cache button at the bottom of the screen. Integrator will reconnect to the data object and attempt to reread field names. You can always manually enter the object name in this field.
The default mapping
If there is no mapping, the destination fields will be exactly the same as the source fields.
If a source field is not part of the mapping, it will be automatically added to the destination (default mapping).
A source field must be manually excluded in order to not appear in the destination.
Exclude a field
A field must be manually excluded in order to not appear in the destination.
Select or enter the SOURCE field, click the
Exclude check box to the right.
Select or enter the DESTINATION field, click the
Add a pair of source and destination fields
To add a new pair of source and destination fields, click the
+ button. Select or enter the SOURCE and DESTINATION field names.
Add a field to the destination which does not exist in the source
To add a field to the destination which does not exist in the source, click the add field button, enter the DESTINATION field name and click the
Add Field checkbox. Continue by clicking the
Exclude a field from mapping
To exclude a field from manual mapping, simple delete it. The system will fall back to its default mapping.
Change the field data type
By default, the destination field gets its data type from the source field. To change the destination data type, click the
Data type button, select the "Data type" from the drop-down, or if needed, enter a "Database specific type" (for example,
varchar(255)). You can also specify if the field is
Integrator can automatically create a default mapping by simply reading the fields from the source object and mapping them to the same fields in the destination. You can then manually change the source and destination field names.
Create mapping overrides the current mapping.
You can remove all manual mapping by clicking the
Remove mapping button.
Working with nested datasets
The output from most of the web services is nested. For example, when ORDER is returned from the API, it contains information about the order itself, as well as all items included in the order.
When Integrator reads a nested source data object, it parses it and represents the fields in a tree-like structure:
As you can see in the figure above, the dimensions (inner data sets) are test and phoneNumbers. Use the buttons
Make this field a child of the one above and
Move child field up one level to control the level of nestedness for a specific field. You can also drag and drop fields up and down.
at this time, the mapping editor supports nested data objects only for the source. Integrator itself includes multiple techniques for creating nested destination objects.
Read more about working with complex nested datasets.