Mapping Rules within a mapping group are applied to the data in the order specified by the Position field.

When a Mapping Group is assigned to a column in a data payload or sample file, each Mapping Rule of the Mapping Group is evaluated for each row until a matching rule is found. Once a Mapping Rule is found, the value in the row is transformed by the Mapping Rule and processing for that row is complete.

This is especially important to understand when there are multiple mapping rules which can be applied to a value. The Position field of a Mapping Rule allows a specific order to be defined to account for exceptions to a general rule.

Example:

There are two Mapping Rules. One says a value of "100011" is mapped to "Short Term Investments". The other says anything that begins with "1000*" is mapped to "Cash".

Q: How would these rules be processed?

A: The Mapping Rule for "Cash" could apply to either account value, because its value (1000*) is also satisfied by that of "Short Term Investments" (100011).

To address overlapping definitions, the Position field sets the priority of the Mapping Rule for "Short Term Investments" higher than that of "Cash".

From

To

Position

100011

Short Term Investments

1

1000*

Cash

2

The Mapping Rule type - EXACT, LIKE, REGEX - has no bearing on the processing order. Mapping Rules can be ordered regardless of their type.


📚 Related Topics from this Section:

Pipelines

Mapping Groups

Mapping Types


Did this answer your question?