Mappers

This section shows all mappers configured for the selected IM instance.

Instance Repository tab shows already deployed mappers.
Workspace tab shows new or locally edited mappers that have not been deployed yet.

Working with mappers:

To see how a mapper is defined, click the row option Show Definition in the Instance Repository tab. The definition is read-only.
The definition can be viewed also for failed mappers, so that the user can see the code and troubleshoot it.
To change a mapper, create a local copy, edit it in the Workspace and deploy it.
Note: Mappers which use converter or predicate cannot currently be edited in PlatformManager UI.

For more information regarding the converters you can use in the mappers, see Advanced Field Editor.

When you create a new mapper, you also have the option to import its XML definition (so that you do not have to set it up manually).

The standard case is that there is just one mapper in the definition file. But it is also possible to switch to the legacy mode and allow having multiple mappers in the file (by setting the field isStandard to false). These so called non-standard mappers cannot be edited by users at all (no local copy, delete or modify) as they are not compatible with PlatformManager UI.
Non-standard mappers are marked with an info icon, so that their status is immediately visible.

Edit Mapper Dialog

For general mapper setup, see the IntegrationManager documentation.

Here, you have these additional options:

For loadMapper you can:
- Send empty values as either an empty string ("") or as NULL.
- Define which properties should be excluded.
- Allow the possibility to include unmapped properties (then no mapping is needed and you can save an empty mapper).
- Skip invalid records.
For integrateMapper you can:
- Include NULLs.

In export mappers, the row order can be changed by drag & drop.