-
Notifications
You must be signed in to change notification settings - Fork 82
mapping
Icon |
|
---|---|
Use When |
Data needs to be mapped from one set of entities/attributes (model structure) to another set of entities/attributes |
Samples |
Flat File to Relational Database, Normalized Table to Denormalized File, Partition by Gender |
Description |
The mapping component allows you to map messages from one model structure to another. |
Inbound Message Type |
Model Based Message |
Output Message Type |
Model Based Message |
Control Message Handling |
Input: As entity messages are received this component will process the data. Output: A single control message will be forwarded to downstream components once all messages have been processed through this step. |
Name | Description |
---|---|
Whether to forward failed messages and continue processing. This is the name of a linked component to forward the failed messages to. |
|
Set Unmapped Attributes To Null |
Whether attributes in the output model that don’t have a mapping specified from the input model should be set to null. |
Entity Per Record |
Determines whether inbound records will be split into multiple output records, one for each entity. Defaults to false. If set, the output model will have null values for every entity/attribute combination that is in the output model but not mapped from the input model. If not set, the output model will not contain entities/attributes that are not mapped from the input model. |
Double clicking on the Mapping component in the flow will result in the Mapping editor being displayed as shown below.
The Mapping editor displays the input model on the left hand side of the screen, and the output model on the right hand side of the screen. Data can be mapped from the input model to the output mode by:
-
Clicking on an attribute in the input model and dragging until your mouse cursor is over the desired output model attribute
-
Clicking on an attribute in the input model, then clicking again on the desired output model attribute
Tip
|
For large models, typing an entity or attribute name in the Filter box will narrow the displayed model to entites or attributes matching the Filter criteria. |
The AutoMap feature will look at both input and output models and attempt to map the models based on similarly named attributes. It first attempts to find an exact entity/attribute match, if not, it will look for an attribute name match starting with the top entity on the source comparing with the target. Next, it will perform a fuzzy match starting again from the top looking for any similarly named attributes. You can apply filtering to your entities displayed and the AutoMap will honor only mapping the entities visible.