---
title: "Map Values Operator"
slug: "map-values-operator"
description: "Update multiple values in a table with the Map Values operator for data normalization, ensuring consistency and accuracy across your datasets."
updated: 2025-10-28T13:24:58Z
published: 2025-10-28T13:24:58Z
canonical: "docs.unqork.io/map-values-operator"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unqork.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Map Values Operator

UDesignerClassic Designer

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(77).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)

The **Map Values operator** updates multiple values in a table. Using a mapping table, you can quickly modify many values across multiple keys in a single step. This process is known as data normalization, which enables you to introduce consistency and accuracy across module data.

Use the Map Values operator to:

- values before presenting them to your end-user. For example, convert text from camel case title or sentence case.
- Refresh values imported from external or outdated sources.
- Standardize data across multiple data sets.
- Align similar values within a single data set, such as correcting spelling variations or abbreviations.

You’ll find the Map Values operator under the [Table](https://docs.unqork.io/docs/table-operators) group to the left of the [Data Workflow](https://docs.unqork.io/docs/unqorks-data-workflow-operators) canvas.

### Similar Data Workflow Operators

The Map Values, Map Keys, and Create Field operators are closely related but serve different purposes.

Here are the comparisons:

- **Map Keys operator**: The Map Keys operator updates the *keys* in a set of key/value pairs. In comparison, Map Values updates the *values* in a set of key/value pairs.
- **Create Field operator**: Similar to Map Values, Create Field can also update values in key/value pairs. However, Create Field lets you use conditional logic with statements and doesn’t rely on a mapping table. Instead, you define the value changes directly in the operator’s Info window.

## About the Info Window

Here's a breakdown of each setting in the Map Values operator’s Info window:

| Setting | Description |
| --- | --- |
| Category | Grayed out and non-adjustable setting indicating the operation type. |
| Label | Sets the label for your operator, displaying below the operator on your Data Workflow canvas. This field is optional, but set a label if you use more than one of the same operator type. A label helps you identify your operators without opening any Info windows. |
| Preserve Argument Type | When selected, this setting ensures the argument data type is respected when the operator executes. |
| Source Column | Enter the name (column header) of the column in your mapping table that defines the original values. |
| Target Column | Enter the name (column header) of the column in your mapping table that defines the new values. |
| Keys | Enter which keys contain values you want the operator to update, according to the mapping table. To list multiple keys, use a comma-separated list. If left empty, the operator updates all keys with values that match the mapping table. |

## Adding a Map Values Operator

In this example, you'll use the Map Values operator to update values in a table. You'll also explore the importance of using the operator's **Keys** setting when the same value exists across multiple keys. Because the Map Values operator updates table-based data, begin by configuring a Data Table component.

> [!TIP]
> You can use the Map Values operator with any table-based data, not just data created with a Data Table component. For example, you can use Map Values with data returned by the List Submissions for Dashboard API call. In that case, set up a Hidden component to store the data returned by the Plug-In running the API call. Then, use a simple -to- Data Workflow to move the data from Plug-In to Hidden component. The Hidden component is then used as the input in your Map Values Data Workflow.

> [!NOTE]
> These instructions assume you have a new module open, saved, and with a title.

### Configure the First Data Table Component

Configure a [Data Table](https://docs.unqork.io/docs/data-table-component) component that you can use as a data source. It will include location data with the same value in two columns. In this case, the value `CA` refers to both the country Canada and the state California.

1. In the Module Builder, drag and drop a **Data Table** component onto your canvas.
2. In the **Property ID** field, enter `dtData`.
3. In the data table, enter the following:

| # | A | B |
| --- | --- | --- |
| 1 | country | stateprovince |
| 2 | US | CA |
| 3 | US | NY |
| 4 | CA | ON |
| 5 | CA | NS |
| 6 | CA | BC |
| 7 | US | AZ |
| 8 | CA | AB |
| 9 | US | CA |

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(79).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)
4. Click **Save Component**.

### Configure the Second Data Table Component

The second Data Table component is an essential part of using the Map Values operator. Here, you'll create a two-column table that acts as a mapping table. In the first column, `oldValue`, you'll list all the values you want the Map Values operator to update. In the second column, `newValue`, you'll list the new values you want to use. Then, you'll reference the mapping table's column headers in the Map Values operator's Info window. Let's update the abbreviation `US` to be `USA` and the abbreviation `CA` to be `CAN`.

1. Drag and drop a **Data Table** component onto your canvas, placing it below the first **Data Table** component.
2. In the **Property ID** field, enter `dtMapping`.
3. Complete the data table as follows:

| # | A | B |
| --- | --- | --- |
| 1 | oldValue | **newValue** |
| 2 | CA | CAN |
| 3 | US | USA |

> [!NOTE]
> You don't need to include quotation marks around your values.

> [!TIP]
> You can list the values you want to change in any order in the **oldValue** column. As long as the values exist in the data source, the Map Values operator will know to update them.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(80).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)
4. Click **Save Component**.

### Configure the Hidden Component

Next, you'll configure a [Hidden](https://docs.unqork.io/docs/hidden-component) component to store your final data and reference it in your Data Workflow.

1. Drag and drop a **Hidden** component onto your canvas, placing it below the `dtData` and `dtMapping` **Data Table** components.
2. In the **Property ID** and **Label Text** fields, enter `updatedTable`.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(81).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)
3. Click **Save Component**.

### Configure the Data Workflow Component

Next, let's configure the Data Workflow. With the help of your mapping table, it'll use a Map Values operator to update the `CA` and `US` values.

1. Drag and drop a **Data Workflow** component onto your canvas, placing it below the `updatedTable` **Hidden** component.
2. In the **Property ID** and **Canvas Label Text** fields, enter `dwfMapValues`.

#### Configure the Input Operators

1. Drag and drop two **Input** operators onto your Data Workflow canvas.
2. Configure the first Input operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Input |
| Component | dtData |
| Required | Yes |
| Source | Default |
3. Configure the second Input operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Input |
| Component | dtMapping |
| Required | Yes |
| Source | Default |

#### Configure the Console Operators

Next, add a pair of [Console](https://docs.unqork.io/docs/console-operator) operators. These will help you compare the before and after of the Data Workflow. One will display the data before the Map Values operator, and the other will serve as a reminder of how you set up your mapping table.

1. Drag and drop two **Console** operators onto your Data Workflow canvas.
2. Configure the first Console operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Console |
| Label | Mapping Table |
3. Connect the output port (right) of the `dtMapping` **Input** operator to the input port (left) of the `Mapping Table` **Console** operator.
4. Configure the second Console operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Console |
| Label | Before Map Values |
5. Connect the output port (right) of the `dtData` **Input** operator to the input port (left) of the `Before Map Values` **Console** operator.

#### Configure the Map Values Operator

Now you're ready to set up the Map Values operator. Notice that the values you'll enter in the Info window's Source Column and Target Column fields match the column headers in the `dtMapping` **Data Table** component, which is your mapping table. The Source Column field should always reference the column with your old values. The Target Column field should always reference the column with your new values.

> [!TIP]
> The Map Values operator has two input ports. Always connect the data source to the upper input port and the mapping table to the lower input port.

1. Drag and drop a **Map Values** operator onto your Data Workflow canvas.
2. Complete the operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Map Values |
| Label | Map New Value |
| Source Column | oldValue |
| Target Column | newValue |
| Keys | country |

> [!NOTE]
> You need to add country in the Keys field to avoid updating all instances of the value CA to CAN. Remember, your data includes the value CA as a reference to California as well.
3. Connect the output port (right) of the `dtData` **Input** operator to the upper input port (left) of the `Map New Value` **Map Values** operator.
4. Connect the output port (right) of the `dtMapping` **Input** operator to the lower input port (left) of the `Map New Value` **Map Values** operator.

#### Configure the Third Console Operator

Next, let's add another [Console](https://docs.unqork.io/docs/console-operator) operator to display the data after using the Map Values operator, helping you compare the before and after of your Data Workflow.

1. Drag and drop a **Console** operator onto your Data Workflow canvas.
2. Configure the operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Console |
| Label | After Map Values |
3. Connect the output port (right) of the `Map New Value` **Map Values** operator to the input port (left) of the `After Map Values` **Console** operator.

#### Configure the Output Operator

In the last step of the Data Workflow, output your updated table to the Hidden component you created earlier.

1. Drag and drop an **Output** operator onto your Data Workflow canvas.
2. Configure the operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Output |
| Component | updatedTable |
| Action | value |
3. Connect the output port (right) of the `Map New Value` **Map Values** operator to the input port (left) of the `updatedTable` **Output** operator.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(82).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)
4. Click **Save Component**.

### Configure the Button Component

Lastly, configure a Button component that you can click in Express View to trigger your Data Workflow.

1. Drag and drop a **Button** component onto your canvas, placing it below the `dwfMapValues` **Data Workflow** component.
2. In the **Property ID** field, enter `btnRunDWF`.
3. In the **Label Text** field, enter `Run Map Values`.
4. From the **Action Type** drop-down, select **Event**.
5. From the **On Click** drop-down, select **dwfMapValues**.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(83).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)
6. Click **Save Component**.
7. **Save** your module.

Here's how the completed example looks in the Module Builder:

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(84).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)

Here's how the completed example works in Express View. Preview your module in Express View and open the DevTools Console. Click the **Run Map Values** button and view how the data displays in the console.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/dwfMapValues_02_express.gif?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)

It's a good idea to use the Keys setting when updating values that occur across multiple keys. Let's look at what would have occurred if you didn't add country in the Map Values operator's Keys setting. Without specifying a key to update, the operator would have replaced all instances of CA with CAN and included the stateprovince value CA. This means the abbreviation for the state of California would have also changed to CAN. Here's what that would have looked like:

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/dwfMapValues_08_consoleincorrect.jpg?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(85).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)

The **Map Values operator** updates multiple values in a table. Using a mapping table, you can quickly modify many values across multiple keys in a single step. This process is known as data normalization, which enables you to introduce consistency and accuracy across module data.

Use the Map Values operator to:

- values before presenting them to your end-user. For example, convert text from camel case title or sentence case.
- Refresh values imported from external or outdated sources.
- Standardize data across multiple data sets.
- Align similar values within a single data set, such as correcting spelling variations or abbreviations.

You’ll find the Map Values operator under the [Table](https://docs.unqork.io/docs/table-operators) group to the left of the [Data Workflow](https://docs.unqork.io/docs/unqorks-data-workflow-operators) canvas.

### Similar Data Workflow Operators

The Map Values, Map Keys, and Create Field operators are closely related but serve different purposes.

Here are the comparisons:

- **Map Keys operator**: The Map Keys operator updates the *keys* in a set of key/value pairs. In comparison, Map Values updates the *values* in a set of key/value pairs.
- **Create Field operator**: Similar to Map Values, Create Field can also update values in key/value pairs. However, Create Field lets you use conditional logic with statements and doesn’t rely on a mapping table. Instead, you define the value changes directly in the operator’s Info window.

## About the Info Window

Here's a breakdown of each setting in the Map Values operator’s Info window:

| Setting | Description |
| --- | --- |
| Category | Grayed out and non-adjustable setting indicating the operation type. |
| Label | Sets the label for your operator, displaying below the operator on your Data Workflow canvas. This field is optional, but set a label if you use more than one of the same operator type. A label helps you identify your operators without opening any Info windows. |
| Preserve Argument Type | When selected, this setting ensures the argument data type is respected when the operator executes. |
| Source Column | Enter the name (column header) of the column in your mapping table that defines the original values. |
| Target Column | Enter the name (column header) of the column in your mapping table that defines the new values. |
| Keys | Enter which keys contain values you want the operator to update, according to the mapping table. To list multiple keys, use a comma-separated list. If left empty, the operator updates all keys with values that match the mapping table. |

## Adding a Map Values Operator

In this example, you'll use the Map Values operator to update values in a table. You'll also explore the importance of using the operator's **Keys** setting when the same value exists across multiple keys. Because the Map Values operator updates table-based data, begin by configuring a Data Table component.

> [!TIP]
> You can use the Map Values operator with any table-based data, not just data created with a Data Table component. For example, you can use Map Values with data returned by the List Submissions for Dashboard API call. In that case, set up a Hidden component to store the data returned by the Plug-In running the API call. Then, use a simple -to- Data Workflow to move the data from Plug-In to Hidden component. The Hidden component is then used as the input in your Map Values Data Workflow.

> [!NOTE]
> These instructions assume you have a new module open, saved, and with a title.

### Configure the First Data Table Component

Configure a [Data Table](https://docs.unqork.io/docs/data-table-component) component that you can use as a data source. It will include location data with the same value in two columns. In this case, the value `CA` refers to both the country Canada and the state California.

1. In the Module Builder, drag and drop a **Data Table** component onto your canvas.
2. In the **Label** and **Property Name** fields, enter `dtData`.
3. In the data table, enter the following:

| # | A | B |
| --- | --- | --- |
| 1 | country | stateprovince |
| 2 | US | CA |
| 3 | US | NY |
| 4 | CA | ON |
| 5 | CA | NS |
| 6 | CA | BC |
| 7 | US | AZ |
| 8 | CA | AB |
| 9 | US | CA |

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/dwfMapValues_03_dtData.jpg?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)
4. Click **Save**.

### Configure the Second Data Table Component

The second Data Table component is an essential part of using the Map Values operator. Here, you'll create a two-column table that acts as a mapping table. In the first column, `oldValue`, you'll list all the values you want the Map Values operator to update. In the second column, `newValue`, you'll list the new values you want to use. Then, you'll reference the mapping table's column headers in the Map Values operator's Info window. Let's update the abbreviation `US` to be `USA` and the abbreviation `CA` to be `CAN`.

1. Drag and drop a **Data Table** component onto your canvas, placing it below the `dtData` **Data Table** component.
2. In the **Label** and **Property Name** fields, enter `dtMapping`.
3. Complete the data table as follows:

| # | A | B |
| --- | --- | --- |
| 1 | oldValue | newValue |
| 2 | CA | CAN |
| 3 | US | USA |

> [!NOTE]
> You don't need to include quotation marks around your values.

> [!TIP]
> You can list the values you want to change in any order in the `oldValue` column. As long as the values exist in the data source, the Map Values operator will know to update them.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/dwfMapValues_04_dtMapping.jpg?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)
4. Click **Save**.

### Configure the Hidden Component

Next, you'll configure a [Hidden](https://docs.unqork.io/docs/hidden-component) component to store your final data and reference it in your Data Workflow.

1. Drag and drop a **Hidden** component onto your canvas, placing it below the `dtData` and `dtMapping` **Data Table** components.
2. In the **Property ID** and **Canvas Label Text** fields, enter `updatedTable`.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(86).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)
3. Click **Save**.

### Configure the Data Workflow Component

Next, let's configure the Data Workflow. With the help of your mapping table, it'll use a Map Values operator to update the `CA` and `US` values.

1. Drag and drop a **Data Workflow** component onto your canvas, placing it below the `updatedTable` **Hidden** component.
2. In the **Canvas Label Text** and **Property Name** fields, enter `dwfMapValues` .

#### Configure the Input Operators

1. Drag and drop two **Input** operators onto your Data Workflow canvas.
2. Configure the first Input operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Input |
| Component | dtData |
| Required | Yes |
| Source | Default |
3. Configure the second Input operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Input |
| Component | dtMapping |
| Required | Yes |
| Source | Default |

#### Configure the Console Operators

Next, add a pair of [Console](https://docs.unqork.io/docs/console-operator) operators. These will help you compare the before and after of the Data Workflow. One will display the data before the Map Values operator, and the other will serve as a reminder of how you set up your mapping table.

1. Drag and drop two **Console** operators onto your Data Workflow canvas.
2. Configure the first Console operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Console |
| Label | Mapping Table |
3. Connect the output port (right) of the `dtMapping` **Input** operator to the input port (left) of the `Mapping Table` **Console** operator.
4. Configure the second Console operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Console |
| Label | Before Map Values |
5. Connect the output port (right) of the `dtData` **Input** operator to the input port (left) of the `Before Map Values` **Console** operator.

#### Configure the Map Values Operator

Now you're ready to set up the Map Values operator. Notice that the values you'll enter in the Info window's Source Column and Target Column fields match the column headers in the `dtMapping` **Data Table** component, which is your mapping table. The Source Column field should always reference the column with your old values. The Target Column field should always reference the column with your new values.

> [!TIP]
> The Map Values operator has two input ports. Always connect the data source to the upper input port and the mapping table to the lower input port.

1. Drag and drop a **Map Values** operator onto your Data Workflow canvas.
2. Complete the operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Map Values |
| Label | Map New Value |
| Source Column | oldValue |
| Target Column | newValue |
| Keys | country |

> [!NOTE]
> You need to add country in the Keys field to avoid updating all instances of the value CA to CAN. Remember, your data includes the value CA as a reference to California as well.
3. Connect the output port (right) of the `dtData` **Input** operator to the upper input port (left) of the `Map New Value` **Map Values** operator.
4. Connect the output port (right) of the `dtMapping` **Input** operator to the lower input port (left) of the `Map New Value` **Map Values** operator.

#### Configure the Third Console Operator

Next, let's add another [Console](https://docs.unqork.io/docs/console-operator) operator to display the data after using the Map Values operator, helping you compare the before and after of your Data Workflow.

1. Drag and drop a **Console** operator onto your Data Workflow canvas.
2. Configure the operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Console |
| Label | After Map Values |
3. Connect the output port (right) of the `Map New Value` **Map Values** operator to the input port (left) of the `After Map Values` **Console** operator.

#### Configure the Output Operator

For the last step of the Data Workflow, let's output your updated table to the Hidden component you created earlier.

1. Drag and drop an **Output** operator onto your Data Workflow canvas.
2. Configure the operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Output |
| Component | updatedTable |
| Action | value |
3. ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/dwfMapValues_05_dwf.jpg?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)
  1. Connect the output port (right) of the `Map New Value` **Map Values** operator to the input port (left) of the `updatedTable` **Output** operator.
4. Click **Save**.

### Configure the Button Component

Lastly, configure a Button component that you can click in Express View to trigger your Data Workflow.

1. Drag and drop a Button component onto your canvas, placing it below the `dwfMapValues` **Data Workflow** component.
2. In the **Property ID** field, enter `btnRunDWF`.
3. In the **Label Text** field, enter `Run Map Values`.
4. To the left of the component’s configuration window, click **Actions**.
5. Set the **Action Type** as **Event**.
6. From the **On Click** drop-down, select **dwfMapValues**.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(87).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)
7. Click **Save** **& Close**.
8. **Save** your module.

Here's how the completed example looks in the Module Builder:

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(88).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)

Here's how the completed example works in Express View. Preview your module in Express View and open the DevTools Console. Click the **Run Map Values** button and view how the data displays in the console.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/dwfMapValues_02_express.gif?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)

It's a good idea to use the Keys setting when updating values that occur across multiple keys. Let's look at what would have occurred if you didn't add country in the Map Values operator's Keys setting. Without specifying a key to update, the operator would have replaced all instances of CA with CAN and included the stateprovince value CA. This means the abbreviation for the state of California would have also changed to CAN. Here's what that would have looked like:

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/dwfMapValues_08_consoleincorrect.jpg?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A06Z&se=2026-11-09T04%3A51%3A06Z&sr=c&sp=r&sig=GViXGSWc1ik5HQzzDQOmOWnmedwKoJRDve1M3osewIw%3D)

A key-value pair is a fundamental data structure where a unique "key" is associated with a specific "value," used for organizing and retrieving data efficiently, like in dictionaries or databases.

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.

A naming convention for computer programming. Use camelCase for Property IDs, for example: newUser, lastName, & rdoButton.

A key-value pair is a fundamental data structure where a unique "key" is associated with a specific "value," used for organizing and retrieving data efficiently, like in dictionaries or databases.

A key-value pair is a fundamental data structure where a unique "key" is associated with a specific "value," used for organizing and retrieving data efficiently, like in dictionaries or databases.

Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field.

APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services.

A Property ID is the unique field ID used by Unqork to track and link components in your module.

Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field.

Canvas Label Text indicates the purpose of the corresponding field or component. For non-input components, the Canvas Label Text isn't end-user facing, and only appears in the .

Express View is how your end-user views your application. Express View also lets you preview your applications to test your configuration and view the styling. This is also the view your end-users will see when interacting with your application. After configuring a module, click Preview in the Module Builder to interact with the module in Express View.

Triggers activate another component when certain requirements are met. Trigger types include Concurrent, Post, and Error. Some components do not have the ability to trigger others.

The action performed by the button when selected.

DOM (Document Object Model) events are signals or notifications that something has occurred or is occurring within a web page, often triggered by user interactions or by the browser itself. These events allow JavaScript to react to changes and interactions on a web page, making it dynamic and interactive.

Enter the Property ID of the component that you want to trigger on each button-click.

A Property ID is the unique field ID used by Unqork to track and link components in your module.

## Related

- [Data Workflow Component](/data-workflow-component.md)
- [Introduction to Data Workflow](/introduction-to-data-workflow.md)