---
title: "Map Keys Operator"
slug: "map-keys-operator"
description: "Update your table keys effortlessly with the Map Keys operator, aligning and renaming data for clarity and consistency in your workflows."
updated: 2025-10-28T13:24:02Z
published: 2025-10-28T13:24:02Z
canonical: "docs.unqork.io/map-keys-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 Keys Operator

UDesignerClassic Desginer

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

The **Map Keys** operator updates multiple key names in a table. For example, imagine you have a [Data Table](https://docs.unqork.io/docs/data-table-component) component using column headers named `name1`, `name2`, `age`, and `income`. You can rename keys like `name1` and `name2` to `firstName` and `lastName` using the Map Keys operator**.** It uses a mapping table that specifies which keys to replace and their new names. The operator automatically applies these updates across all objects in your array.

> Tables store as an array of objects, with each object representing one row. Each column and its corresponding value in that row form a key/value pair.

Examples of when to use the Map Keys operator include:

- Removing spaces from key names to prevent future errors.
- Aligning key names from imported data with your current naming standards.
- Renaming confusing or unclear keys when presenting data to end-users. For example, converting camel case to title case before exporting to .
- Simplifying long or complex key names from external API data to make them easier to reference in your workflows.

You’ll find the Map Keys 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 Keys, Map Values, and Create Field operators are closely related but serve different purposes.

Here are the comparisons:

- **Map Values operator**: The Map Values operator lets you update the values in a set of key/value pairs. By comparison, the Map Keys operator lets you update the keys in a set of key/value pairs.
- **Create Field operator**: Similar to the Map Values operator, the Create Field operator can update values in key/value pairs. However, the Create Field operator lets you use conditional logic with statements and does not 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 Keys 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 key names. |
| Target Column | Enter the name (column header) of the column in your mapping table that defines the new key names. |

## Adding a Map Keys Operator

In this example, use a Map Keys operator to update the keys in key/value pairs in an array of objects. Because the Map Keys operator lets you update table-based data, begin by configuring a [Data Table](https://docs.unqork.io/docs/data-table-component) component.

> [!TIP]
> You can use the Map Keys operator with any table-based data, not just data from a Data Table component. For example, you can use the operator with data returned by the List Submissions for Dashboard API call. You can set up a Hidden component to store the data from the API call. Then, you'll 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 Keys 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 can be used as a data source. Create sample column headers that you can update later.

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 | C | D |
| --- | --- | --- | --- | --- |
| 1 | name1 | name2 | age | income |
| 2 | Minna | Amigon | 34 | 77000 |
| 3 | Mitsue | Tollner | 46 | 102000 |
| 4 | Abel | Maclead | 31 | 65000 |
| 5 | Sage | Wieser | 49 | 121000 |

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

### Configure the Second Data Table Component

Create a two-column table that acts as a mapping table. In the first column, `oldKey`, list all the keys you want the Map Keys operator to update. In the second column, `newKey`, list the new key names. Then, reference the mapping table's column headers in the Map Keys operator's Info window. Let's update the `name1` key to be `firstName` and the `name2` key to be `lastName`.

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

| # | A | B |
| --- | --- | --- |
| 1 | oldKey | newKey |
| 2 | name1 | firstName |
| 3 | name2 | lastName |

> [!TIP]
> You can list the keys you want to change in any order in the **oldKey** column. As long as the keys exist in the data source, the Map Keys operator will know to update them. You don't need to include quotation marks around your key names.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(96).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A09Z&se=2026-11-09T04%3A51%3A09Z&sr=c&sp=r&sig=mAM6%2Fiz0h%2FuBVwwMY%2Bjkc0sRDouv5yuJtj6%2BPgAEQXg%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 table. You'll reference it later 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(98).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A09Z&se=2026-11-09T04%3A51%3A09Z&sr=c&sp=r&sig=mAM6%2Fiz0h%2FuBVwwMY%2Bjkc0sRDouv5yuJtj6%2BPgAEQXg%3D)
3. Click **Save Component**.

### Configure the Data Workflow Component

Next, let's create the Data Workflow. With the help of your mapping table, the Map Keys operator in the Data Workflow will update the `name1` and `name2` keys.

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 `dwfMapKeys`.

#### 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 so you can compare the before and after of the Data Workflow. One will display the data before using Map Keys, 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 Keys |
5. Connect the output port (right) of the `dtData` **Input** operator to the input port (left) of the `Before Map Keys` **Console** operator.

#### Configure the Map Keys Operator

Now you're ready to set up the Map Keys 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.

> [!TIP]
> The Map Keys 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 Keys** operator onto your Data Workflow canvas.
2. Complete the operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Map Keys |
| Label | Map New Key |
| Source Column | oldKey |
| Target Column | newKey |
3. Connect the output port (right) of the `dtData` **Input** operator to the upper input port (left) of the `Map New Key` **Map Keys** operator.
4. Connect the output port (right) of the `dtMapping` **Input** operator to the lower input port (left) of the `Map New Key` **Map Keys** operator.

#### Configure the Third Console Operator

Next, let's add another [Console](https://docs.unqork.io/docs/console-operator) operator that displays the data after it passes through the Map Keys 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 Keys |
3. Connect the output port (right) of the `Map New Key` **Map Keys** operator to the input port (left) of the `After Map Keys` **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 Key` **Map Keys** operator to the input port (left) of the `updatedTable` **Output** operator.

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

### Configure the Button Component

Lastly, configure a [Button](/v1/docs/button-component) 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 `dwfMapKeys` **Data Workflow** component.
2. In the **Property ID** field, enter `btnRunDWF`.
3. In the **Label Text** field, enter `Run Map Keys`.
4. From the **Action Type** drop-down, select **Event**.
5. From the **On Click** drop-down, enter or select `dwfMapKeys`.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(99).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A09Z&se=2026-11-09T04%3A51%3A09Z&sr=c&sp=r&sig=mAM6%2Fiz0h%2FuBVwwMY%2Bjkc0sRDouv5yuJtj6%2BPgAEQXg%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(100).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A09Z&se=2026-11-09T04%3A51%3A09Z&sr=c&sp=r&sig=mAM6%2Fiz0h%2FuBVwwMY%2Bjkc0sRDouv5yuJtj6%2BPgAEQXg%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 Keys** button and view the results in the console.

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

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

The **Map Keys** operator updates multiple key names in a table. For example, imagine you have a [Data Table](https://docs.unqork.io/docs/data-table-component) component using column headers named `name1`, `name2`, `age`, and `income`. You can rename keys like `name1` and `name2` to `firstName` and `lastName` using the Map Keys operator**.** It uses a mapping table that specifies which keys to replace and their new names. The operator automatically applies these updates across all objects in your array.

> Tables store as an array of objects, with each object representing one row. Each column and its corresponding value in that row form a key/value pair.

Examples of when to use the Map Keys operator include:

- Removing spaces from key names to prevent future errors.
- Aligning key names from imported data with your current naming standards.
- Renaming confusing or unclear keys when presenting data to end-users. For example, converting camel case to title case before exporting to .
- Simplifying long or complex key names from external API data to make them easier to reference in your workflows.

You’ll find the Map Keys 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 Keys, Map Values, and Create Field operators are closely related but serve different purposes.

Here are the comparisons:

- **Map Values operator**: The Map Values operator lets you update the values in a set of key/value pairs. By comparison, the Map Keys operator lets you update the keys in a set of key/value pairs.
- **Create Field operator**: Similar to the Map Values operator, the Create Field operator can update values in key/value pairs. However, the Create Field operator lets you use conditional logic with statements and does not 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 Keys 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. |
| Source Column | Enter the name (column header) of the column in your mapping table that defines the original key names. |
| Target Column | Enter the name (column header) of the column in your mapping table that defines the new key names. |

## Adding a Map Keys Operator

In this example, use a Map Keys operator to update the keys in key/value pairs in an array of objects. Because the Map Keys operator lets you update table-based data, begin by configuring a [Data Table](https://docs.unqork.io/docs/data-table-component) component.

> [!TIP]
> You can use the Map Keys operator with any table-based data, not just data from a Data Table component. For example, you can use the operator with data returned by the List Submissions for Dashboard API call. You can set up a Hidden component to store the data from the API call. Then, you'll use a simple Input-to-Output Data Workflow to move the data from Plug-In to Hidden component. The Hidden component is then used as the input in your Map Keys 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 can be used as a data source. Create sample column headers that you can update later.

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 | C | D |
| --- | --- | --- | --- |
| name1 | name2 | age | income |
| Minna | Amigon | 34 | 77000 |
| Mitsue | Tollner | 46 | 102000 |
| Abel | Maclead | 31 | 65000 |
| Sage | Wieser | 49 | 121000 |

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

### Configure the Second Data Table Component

Create a two-column table that acts as a mapping table. In the first column, `oldKey`, list all the keys you want the Map Keys operator to update. In the second column, `newKey`, list the new key names. Then, reference the mapping table's column headers in the Map Keys operator's Info window. Let's update the `name1` key to be `firstName` and the `name2` key to be `lastName`.

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. In the data table, enter the following:

| A | B |
| --- | --- |
| oldKey | newKey |
| name1 | firstName |
| name2 | lastName |

> [!TIP]
> You can list the keys you want to change in any order in the **oldKey** column. As long as the keys exist in the data source, the Map Keys operator will know to update them. You don't need to include quotation marks around your key names.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/dwfMapKeys_04_dtNewKeys.jpg?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A09Z&se=2026-11-09T04%3A51%3A09Z&sr=c&sp=r&sig=mAM6%2Fiz0h%2FuBVwwMY%2Bjkc0sRDouv5yuJtj6%2BPgAEQXg%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 table. You'll reference it later 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(102).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A09Z&se=2026-11-09T04%3A51%3A09Z&sr=c&sp=r&sig=mAM6%2Fiz0h%2FuBVwwMY%2Bjkc0sRDouv5yuJtj6%2BPgAEQXg%3D)
3. Click **Save**.

### Configure the Data Workflow Component

Next, let's create the Data Workflow. With the help of your mapping table, the Map Keys operator in the Data Workflow will update the `name1` and `name2` keys.

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 `dwfMapKeys`.

#### Configure the Input Operators

1. Drag and drop two [Input operators](https://docs.unqork.io/docs/input-operator) 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 so you can compare the before and after of the Data Workflow. One will display the data before using Map Keys, 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 Keys |
5. Connect the output port (right) of the `dtData` **Input** operator to the input port (left) of the `Before Map Keys` **Console** operator.

#### Configure the Map Keys Operator

Now you're ready to set up the Map Keys 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.

> [!TIP]
> The Map Keys 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 Keys** operator onto your Data Workflow canvas.
2. Complete the operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Map Keys |
| Label | Map New Key |
| Source Column | oldKey |
| Target Column | newKey |
3. Connect the output port (right) of the `dtData` **Input** operator to the upper input port (left) of the `Map New Key` **Map Keys** operator.
4. Connect the output port (right) of the `dtMapping` **Input** operator to the lower input port (left) of the `Map New Key` **Map Keys** operator.

#### Configure the Third Console Operator

Next, let's add another [Console](https://docs.unqork.io/docs/console-operator) operator that displays the data after it passes through the Map Keys 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 Keys |
3. Connect the output port (right) of the `Map New Key` **Map Keys** operator to the input port (left) of the `After Map Keys` **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 Key` **Map Keys** operator to the input port (left) of the `updatedTable` **Output** operator.

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

### Configure the Button Component

Lastly, configure a [Button](/v1/docs/button-component) 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 `dwfMapKeys` **Data Workflow** component.
2. In the **Property ID** field, enter `btnRunDWF`.
3. In the **Label Text** field, enter `Run Map Keys`.
4. To the left of the component’s configuration window, click **Actions**.
5. Set the **Action Type** as **Event**.
6. In the **On Click** drop-down, select **dwfMapKeys**.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(107).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A09Z&se=2026-11-09T04%3A51%3A09Z&sr=c&sp=r&sig=mAM6%2Fiz0h%2FuBVwwMY%2Bjkc0sRDouv5yuJtj6%2BPgAEQXg%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(108).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A09Z&se=2026-11-09T04%3A51%3A09Z&sr=c&sp=r&sig=mAM6%2Fiz0h%2FuBVwwMY%2Bjkc0sRDouv5yuJtj6%2BPgAEQXg%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 Keys** button and view the results in the console.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/dwfMapKeys_02_expressgif.gif?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A09Z&se=2026-11-09T04%3A51%3A09Z&sr=c&sp=r&sig=mAM6%2Fiz0h%2FuBVwwMY%2Bjkc0sRDouv5yuJtj6%2BPgAEQXg%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.

An object is a type of data structure that represents a single, self-contained entity that acts as a container for the characteristics of that entity.

An array is a type of object that stores one or more data types. Data types supported in arrays include numbers, strings, and objects.

An object is a type of data structure that represents a single, self-contained entity that acts as a container for the characteristics of that entity.

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.

In Unqork, an External API (application programming interfaces) connects to services outside of the Unqork platform. APIs 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.

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.

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

The DevTools Console helps you securely store, build, test, and deploy your software.

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

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)