LOOKUP
Category: Filtering & data shaping
Overview
Description | Performs an approximate match lookup in one column and returns the corresponding value from another column. Use when you need threshold-based or approximate mapping from one value range to another. |
Syntax |
|
Parameters |
|
Limitations |
|
Examples
Approximate threshold lookup
This example looks up a salary against an ordered threshold table and returns the corresponding tax value.
The lookup uses one node for the value to search, one node for the sorted index, and one node for the returned result.
Input node: Lookup Value
| Employee | Salary |
|---|---|
| E1 | 50.000 |
Input node: Index
| Sequence | Threshold |
|---|---|
| 0 | 0 |
| 1 | 10.000 |
| 2 | 30.000 |
| 3 | 60.000 |
Input node: Return Value
| Sequence | Tax |
|---|---|
| 0 | 0 |
| 1 | 0 |
| 2 | 1.000 |
| 3 | 2.000 |
| 4 | 3.000 |
Formula: LOOKUP('Lookup Value', 'Index', 'Return Value')
| Employee | → LOOKUP Result |
|---|---|
| E1 | 1.000 |
Expanding the Sequence Dimension
The sequence dimension is a default dimension that defines the steps of a time value. In rare cases, it can be helpful or even necessary to edit the sequence dimension to support complex scenarios on a monthly level.
Additional information on the sequence dimension and how to modify it can be found here: Configure the Sequence Dimension
Related Functions
| Function | When to use instead |
|---|---|
| FILTER | When you want to filter rows by explicit criteria instead of mapping one value range to another through an ordered index table. |
| IF | When you want explicit conditional branching logic instead of using an approximate lookup table. |