lookup
Icon |
|
|---|---|
Use When |
Reference data exists that needs to be looked up / retrieved by a specified key, and another attribute of the the resulting reference data passed to downstream components. |
Samples |
|
Description |
The Lookup component receives reference data from a source component, and then uses that reference data as a lookup source for data coming from another source component. |
Inbound Message Type |
Model Based Message |
Output Message Type |
Model Based Message |
Control Message Handling |
Input: Messages received from the 'Lookup Data Source' input link are collected in a map until a control message is received from this link. Then all other input messages are processed and forwarded. Output: A single control message will be forwarded to downstream components once all files 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. |
|
Lookup Data Source |
The source component that will send reference data (to be looked up) to the Lookup component |
Lookup Key Attribute |
The model attribute in the reference data that will be used as the lookup key to the reference data |
Lookup Value Attribute |
The model attribute in the reference data that will be passed back from the lookup request |
Replacement Key Attribute |
The model attribute that will be used to lookup data from the Lookup Data Source. This value will be matched to the Lookup Key Attribute |
Replacement Value Attribute |
The model attribute that will be replaced by the Lookup Key Value from the resultant row in the Lookup Data Source |
|
Tip
|
Ensure Lookup Key Attribute and Replacement Key Attribute are of the same data type, or the lookup will not work. I.E. model based messages are passed into the lookup component. These two keys must have the same data type in order to compare properly. |