Data Mapper Rules (Magic xpi 3.x)

This topic describes the mapping rules which are enforced by Magic xpi’s Data Mapper.

Introduction

The Data Mapper deals with mapping issues on two levels:

1. Single element – The following elements are considered to be single elements:

   1. An element with the Max occurrences node property set to 1

   2. An element with a filter

   3. Duplicate node

   4. A compound element at the Destination with no mapping

2. Compound element – The following elements are considered to be compound elements:

   1. An element with children elements

   2. An element with the Max occurrences node property greater than 1

You can map the following elements displayed in the Data Mapper screen:

• One Source compound element to a Destination compound element. Mapping a compound element tells the Data Mapper to execute the Destination compound element the same number of times as the Source compound element.

• Single Source multiple simple elements to one Destination simple element (if the Destination type is XML or Template).

• Source compound elements can be mapped to a variable compound element.

• Most sibling elements can be mapped. See below for more information.

Simple data mapping is done automatically by the Data Mapper. You do not need to create an expression.

compound data mapping is carried out by:

• Using the Destination member data expression. The expression can include variables and functions and simple elements from the Source XML connected to the Destination element.

Or

• Using the Expression Editor to call external Java, uniPaaS, or DLL code. This option is used for compound data mapping that needs an external function call.

Related Topics

Data Mapping Scenarios

Data Mapping Considerations