You are here:
Value Map
A reusable lookup table that maps source values to target values.
Required Editions
| View supported editions. |
Use value maps to centralize value translation logic and reuse mappings across flows. When you update a value map, all flows that reference it use the latest mappings.
| Field | Description |
|---|---|
| API Name | The requirement for uniqueness applies only to elements within the current flow. Two elements can have the same API name, provided they're used in different flows. An API name can include underscores and alphanumeric characters without spaces. It must begin with a letter and can’t end with an underscore. It also can’t have two consecutive underscores. |
| Description | Explains the purpose of the value map. |
| Source Data Type | The data type of input values that the value map looks up. |
| Target Data Type | The data type of output values that the value map returns. |
| Value Map Entries | Each entry contains a source value and its mapped target value. |
| Default Behavior | Specifies how the flow handles an unmapped source value. |
Default Behavior Options for Unmapped Values
| Option | Behavior |
|---|---|
| Fail the flow | If the value map lacks the source value, the flow fails at run time. |
| Pass through as an unmapped value | If no mapping exists, the flow outputs the source value. |
| Define a default value | If no mapping exists, the flow uses the configured default target value. Without a default value, the flow passes through the source value. |
Did this article solve your issue?
Let us know so we can improve!
