---
title: "Unwind Operator"
slug: "unwind-operator"
updated: 2025-09-26T05:55:15Z
published: 2025-09-26T05:55:15Z
canonical: "docs.unqork.io/unwind-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.

# Unwind Operator

UDesignerClassic Designer

## Overview

The **Unwind operator** raises the values in a nested array to the next level.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/unwindOperator_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A43Z&se=2026-11-07T18%3A57%3A43Z&sr=c&sp=r&sig=M0%2FzFGDZ%2FaRi933THJ6dtwu9op%2FnixPC55BFDaFEPxw%3D)

For example, begin with the following array:

```json
[
  {
    "key1": "A",
    "key2": "B",
    "key3": [
      "C"
    ]
  }
]
```

In Lines 5 and 6, the `"key3"` key contains an nested array as its value. After using the Unwind operator in a [Data Workflow](/v1/docs/data-workflow-component) component, the value `"C"` in the `"key3"` nested array raises to the same level of the data structure as the values "A" and "B". The final array looks like the following:

```plaintext
[
  {
    "key1": "A",
    "key2": "B",
    "key3": "C"
  }
]
```

Now, all three values are at the same level of the data structure.

You'll find the Get operator under the [Table](/v1/docs/tableoperators) group to the left of the [Data Workflow](/v1/docs/data-workflow-component) canvas.

## About the Info Window

Learn more about each setting in the Unwind 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. |
| **Keep Embedding** | Specifies whether to keep the original, nested key in the final, unwound array. When set to **Yes**, the value(s) in the nested array displays in the unwound array paired with the original nested key. When set to **No**, the values in the nested array separate out. Once separated, they index into the higher level array. > [!NOTE] > The Keep Embedding setting works somewhat differently when unwinding an array of objects. To see examples of how Keep Embedding works with nested objects versus arrays of values, view the [How Unwind Works on Different Arrays](/v1/docs/unwind-operator#how-unwind-works-on-different-arrays) section below. |
| **Unwind Key** | Specifies which key contains the nested array you want to bring to a higher level of the data structure. Enter _arg in this field to sort by the value coming into the operator's argument port. For example, let's say you have the following array: `[{"keyA":"A", "keyB":"B", "keyC":["C"]}]`. You'll unwind "keyC" to bring the value in the nested "keyC" array to the same level as the original array. The final, unwound array looks like the following: `[{"keyA":"A", "keyB":"B", "keyC":"C"}]`. |

## Adding an Unwind Operator

In this example, use a [Address Search](/v1/docs/address-search-component) component to collect and store information about an address. Then, use the Unwind operator in a [Data Workflow](/v1/docs/data-workflow-component) component to extract values from the Address Search component's "address" data object.

> [!NOTE]
> The Unqork Training environment contains a preconfigured address service. If you are configuring in a non-Training environment, you might need to [set up an address service](/v1/docs/enabling-address-search-using-address-services).

The `"address"` data object includes commonly-referenced fields, like `city `or `zip`. But, each row of the array also has another nested array called `"types"`. The `"types"` array indicates which category of address information is in that row. For example, the types array can contain the `"street_number"` or `"postal_code_suffix"` values. Unwinding the `"types"` array brings this category value to the same level as the address information itself.

Use the [Filter](/v1/docs/filter-operator) and [Get](/v1/docs/get-operator) operators to retrieve the specific address information. The Filter operator filters information from the "address_components" array by a particular "types" value. For example, you can filter out the row with "types":"street_number". Then, use the Get operator to extract the street number.

### Configure the Address Search Component

Configure an [Address Search](/v1/docs/address-search-component) component to collect the end-user's location. This location stores in an "address" data object.

1. Drag and drop an **Address Search** component onto your canvas.
2. In the Property ID field, enter **address**.
3. In the Label Text field, enter `Address`.
4. Set **Street**, **Street2**, **City**, **State**, **Zip**, and **Country** to ![A toggle switch indicating an on/off state for a user interface element.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 1.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A43Z&se=2026-11-07T18%3A57%3A43Z&sr=c&sp=r&sig=M0%2FzFGDZ%2FaRi933THJ6dtwu9op%2FnixPC55BFDaFEPxw%3D) **(ON)**.
5. Click **Save Component**.

### Configure the Data Workflow Component

With the Address Search component configured, use your Unwind operator to retrieve specific values. In this example, your Data Workflow retrieves the two-letter state and country abbreviations.

1. Drag and drop a **D****ata Workflow** component onto your canvas, placing it below the **address** **Address Search** component.
2. In the Property ID and Canvas Label Text fields, enter `dwfUnwind`.

#### Configure the Input Operator

Connect your Address Search component to the Data Workflow using an Input operator.

1. Drag and drop an **I****nput** operator onto your **D****ata Workflow** canvas.
2. Configure the operator's **Info** window as follows:

| Info |
| --- |
| **Category** | Input |
| **Component** | address |
| **Required** | Yes |
| **Source** | Default |

#### Configure the Get Operator

Connect a Get operator to the `"address_components"` array in the `"address"` data object.

1. Drag and drop a **G****et** operator onto your **D****ata Workflow** canvas.
2. Configure the operator's **Info** window as follows:

| Info |
| --- |
| **Category** | Get |
| **Label** | Get address_components array |
| **Preserve Argument Type** | ☐ (**unchecked**) |
| **Path** | address_components |
3. Connect the output port (right) of the **I****nput** operator to the input port (left) of the **G****et** operator.

#### Configure the Unwind Operator

Use the Unwind operator to unwind the "types" key. Doing so brings the values in the nested "types" array to each row of the "address_components" array.

1. Drag and drop an **U****nwind** operator onto your **D****ata Workflow** canvas.
2. Configure the operator's **Info** window as follows:

| Info |
| --- |
| **Category** | Unwind |
| **Label** | Unwind on types |
| **Preserve Argument Type** | ☐ (**unchecked**) |
| **Keep Embedding** | Yes |
| **Unwind Key** | types |
3. Connect the output port (right) of the **G****et** operator to the input port (left) of the **U****nwind** operator.

#### Configure the Filter Operators

Use two Filter operators to isolate the values you want. Each Filter operator filters according to a specific `"types"` value. After unwinding, there's now a `"types"` value in each row of the array. To determine which `"types"` value to use in the expression, look at the original `"types"` array. For example, the `"types"` value of `"administrative_area_level_1"` corresponds to the State row of information.

1. Drag and drop two **F****ilter** operators onto the **D****ata Workflow** canvas.
2. Configure the first **F****ilter** operator's **Info** window as follows:

| Info |
| --- |
| **Category** | Filter |
| **Label** | Filter State |
| **Do Note Sanitize Formula** | ☐ (**unchecked**) |
| **Preserve Argument Type** | ☐ (**unchecked**) |
| **Expression** | types="administrative_area_level_1" |
3. Connect the output port (right) of the **U****nwind** operator to the input port (left) of the **Filter State** **F****ilter** operator.
4. Configure the second **F****ilter** operator's **Info** window as follows:

| Info |
| --- |
| **Category** | Filter |
| **Label** | Filter Country |
| **Do Note Sanitize Formula** | ☐ (**unchecked**) |
| **Preserve Argument Type** | ☐ (**unchecked**) |
| **Expression** | types="country" |
5. Connect the output port (right) of the **U****nwind** operator to the input port (left) of the **Filter Country** **F****ilter** operator.

#### Configure Additional Get Operators

Use two more Get operators to retrieve a specific value from each filtered row. Each row contains both a "long_name" and "short_name" value. For example, if the State "long_name" value is New York, then the "short_name" is NY. For this example, you'll retrieve the "short_name" value for State and Country.

1. Drag and drop two **G****et** operators onto the **D****ata Workflow** canvas.
2. Configure the first **G****et** operator's **Info** window as follows:

| Info |
| --- |
| **Category** | Get |
| **Label** | Get State short_name |
| **Preserve Argument Type** | ☐ (**unchecked**) |
| **Path** | [0].short_name |
3. Connect the upper output port (right) of the **Filter State** **F****ilter** operator to the input port (left) of this **Get State short_name** **G****et** operator.
4. Configure the second **G****et** operator's **Info** window as follows:

| Info |
| --- |
| **Category** | Get |
| **Label** | Get Country short_name |
| **Preserve Argument Type** | ☐ (**unchecked**) |
| **Path** | [0].short_name |
5. Connect the upper output port (right) of the **Filter Country** **F****ilter** operator to the input port (left) of this **Get Country short_name** **G****et** operator.

#### Configure the Console Operators

Add four Console operators to view the outcome of each step in the process. Connect one Console operator to the first Get operator to view the `"address_components"` array before unwinding. Then, connect another to the Unwind operator to view the `"address_components"` array after unwinding. Lastly, connect two Console operators to the second and third Get operators. These display exactly what values the Data Workflow retrieves from the address data object.

> [!NOTE]
> The second and third Get operators only output to Console operators. Use dedicated Output operators when creating applications. Then, you can connect those Output operators to Hidden components to store the final values for reference elsewhere in an application.

1. Drag and drop four **C****onsole** operators onto the **D****ata Workflow** canvas.
2. Configure the first **C****onsole** operator's **Info** window as follows:

| Info |
| --- |
| **Category** | Console |
| **Label** | Before Unwind |
3. Connect the output port (right) of the **Get address_components array** **G****et** operator to the input port (left) of this **Before Unwind** **C****onsole** operator.
4. Configure the second **C****onsole** operator's **Info** window as follows:

| Info |
| --- |
| **Category** | Console |
| **Label** | After Unwind |
5. Connect the output port (right) of the **Unwind on types** **U****nwind** operator to the input port (left) of this **After Unwind** **C****onsole** operator.
6. Configure the third **C****onsole** operator's **Info** window as follows:

| Info |
| --- |
| **Category** | Console |
| **Label** | State short_name |
7. Connect the output port (right) of the **Get State short_name** **G****et** operator to the input port (left) of this **State short_name** **C****onsole** operator.
8. Configure the fourth **C****onsole** operator's **Info** window as follows:

| Info |
| --- |
| **Category** | Console |
| **Label** | Country short_name |
9. Connect the output port (right) of the **Get Country short_name** **G****et** operator to the input port (left) of this **Country short_name** **C****onsole** operator.
10. Click **Save Component**.

Here's how the completed Data Workflow looks:

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/dwfUnwind_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A43Z&se=2026-11-07T18%3A57%3A43Z&sr=c&sp=r&sig=M0%2FzFGDZ%2FaRi933THJ6dtwu9op%2FnixPC55BFDaFEPxw%3D)

### Configure the Button Component

Create a button so end-users can click it in Express View and trigger the Data Workflow.

1. Drag and drop a **Button** component onto your canvas, placing it below the **dwfUnwind** **D****ata Workflow** component.
2. In the Property ID, enter **btnRunDWF**.
3. In the Label Text, enter `Run DWF Unwind`.
4. Navigate to the **Actions** settings.
5. From the **Action Type** drop-down, select **Event**.
6. From the **On Click** drop-down, enter or select **dwfUnwind**.
7. Click **Save Component**.
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/moduleComplete_thumb_0_0(8).jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A43Z&se=2026-11-07T18%3A57%3A43Z&sr=c&sp=r&sig=M0%2FzFGDZ%2FaRi933THJ6dtwu9op%2FnixPC55BFDaFEPxw%3D)

**Preview** your module in Express View and open the DevTools Console. Enter an address in the **Address** field and click **Run DWF Unwind**.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/consoleLogs_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A43Z&se=2026-11-07T18%3A57%3A43Z&sr=c&sp=r&sig=M0%2FzFGDZ%2FaRi933THJ6dtwu9op%2FnixPC55BFDaFEPxw%3D)

Notice that there are more rows in the **After Unwind** array than in the **Before Unwind** array. Some rows of the original array had two `"types"` values. For example, look at row two of the **Before Unwind** array `"5th Avenue"`. Its `"types"` value is an array with two rows. After unwinding the data, the `"types"` array separates into row two and row three as displayed in the **After Unwind** array.

## Overview

The **Unwind operator** raises the values in a nested array to the next level.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/unwindOperatorClassic_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A43Z&se=2026-11-07T18%3A57%3A43Z&sr=c&sp=r&sig=M0%2FzFGDZ%2FaRi933THJ6dtwu9op%2FnixPC55BFDaFEPxw%3D)

For example, begin with the following array:

```json
[
  {
    "key1": "A",
    "key2": "B",
    "key3": [
      "C"
    ]
  }
]
```

In Lines 5 and 6, the `"key3"` key contains an nested array as its value. After using the Unwind operator in a [Data Workflow](/v1/docs/data-workflow-component) component, the value `"C"` in the `"key3"` nested array raises to the same level of the data structure as the values "A" and "B". The final array looks like the following:

```plaintext
[
  {
    "key1": "A",
    "key2": "B",
    "key3": "C"
  }
]
```

Now, all three values are at the same level of the data structure.

You'll find the Get operator under the [Table](/v1/docs/tableoperators) group to the left of the [Data Workflow](/v1/docs/data-workflow-component) canvas.

## About the Info Window

Learn more about each setting in the Unwind 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. |
| Keep Embedding | Specifies whether to keep the original, nested key in the final, unwound array. When set to **Yes**, the value(s) in the nested array displays in the unwound array paired with the original nested key. When set to **No**, the values in the nested array separate out. Once separated, they index into the higher level array. > [!NOTE] > The Keep Embedding setting works somewhat differently when unwinding an array of objects. To see examples of how Keep Embedding works with nested objects versus arrays of values, view the [How Unwind Works on Different Arrays](/v1/docs/unwind-operator#how-unwind-works-on-different-arrays) section below. |
| Unwind Key | Specifies which key contains the nested array you want to bring to a higher level of the data structure. Enter _arg in this field to sort by the value coming into the operator's argument port. For example, let's say you have the following array: `[{"keyA":"A", "keyB":"B", "keyC":["C"]}]`. You'll unwind "keyC" to bring the value in the nested "keyC" array to the same level as the original array. The final, unwound array looks like the following: `[{"keyA":"A", "keyB":"B", "keyC":"C"}]`. |

## Adding an Unwind Operator

In this example, use a [Address Search](/v1/docs/address-search-component) component to collect and store information about an address. Then, use the Unwind operator in a [Data Workflow](/v1/docs/data-workflow-component) component to extract values from the Address Search component's "address" data object.

> [!NOTE]
> The Unqork Training environment contains a preconfigured address service. If you are configuring in a non-Training environment, you might need to [set up an address service](/v1/docs/enabling-address-search-using-address-services).

The `"address"` data object includes commonly-referenced fields, like `city `or `zip`. But, each row of the array also has another nested array called `"types"`. The `"types"` array indicates which category of address information is in that row. For example, the types array can contain the `"street_number"` or `"postal_code_suffix"` values. Unwinding the `"types"` array brings this category value to the same level as the address information itself.

Use the [Filter](/v1/docs/filter-operator) and [Get](/v1/docs/get-operator) operators to retrieve the specific address information. The Filter operator filters information from the "address_components" array by a particular "types" value. For example, you can filter out the row with "types":"street_number". Then, use the Get operator to extract the street number.

### Configure the Address Search Component

Configure an [Address Search](/v1/docs/address-search-component) component to collect the end-user's location. This location stores in an "address" data object.

1. In the Module Builder, drag and drop an **Address Search** component onto your canvas.
2. In the **Property ID** field, enter **address**.
3. In the **Label** field, enter `Address`.
4. Set **Street**, **Street2**, **City**, **State**, **Zip**, and **Country** to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(43).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A43Z&se=2026-11-07T18%3A57%3A43Z&sr=c&sp=r&sig=M0%2FzFGDZ%2FaRi933THJ6dtwu9op%2FnixPC55BFDaFEPxw%3D) (**checked**).
5. Click **Save**.

### Configure the Data Workflow Component

With the Address Search component configured, use your Unwind operator to retrieve specific values. In this example, your Data Workflow retrieves the two-letter state and country abbreviations.

1. Drag and drop a **D****ata Workflow** component onto your canvas, placing it below the **address** **Address Search** component.
2. In the **Canvas Label Text** and **Property Name** fields, enter `dwfUnwind`.

#### Configure the Input Operator

Connect your Address Search component to the Data Workflow using an Input operator.

1. Drag and drop an **I****nput** operator onto your **D****ata Workflow** canvas.
2. Configure the operator's **Info** window as follows:

| Info |
| --- |
| Category | Input |
| Component | address |
| Required | Yes |
| Source | Default |

#### Configure the Get Operator

Connect a Get operator to the `"address_components"` array in the "address" data object.

1. Drag and drop a **G****et** operator onto your **D****ata Workflow** canvas.
2. Configure the operator's **Info** window as follows:

| Info |
| --- |
| Category | Get |
| Label | Get address_components array |
| Preserve Argument Type | ☐ (**unchecked**) |
| Path | address_components |
3. Connect the output port (right) of the **I****nput** operator to the input port (left) of the **G****et** operator.

#### Configure the Unwind Operator

Use the Unwind operator to unwind the `"types"` key. Doing so brings the values in the nested `"types" `array to each row of the `"address_components"` array.

1. Drag and drop an **U****nwind** operator onto your **D****ata Workflow** canvas.
2. Configure the operator's **Info** window as follows:

| Info |
| --- |
| Category | Unwind |
| Label | Unwind on types |
| Preserve Argument Type | ☐ (**unchecked**) |
| Keep Embedding | Yes |
| Unwind Key | types |
3. Connect the output port (right) of the **G****et** operator to the input port (left) of the **U****nwind** operator.

#### Configure the Filter Operators

Use two Filter operators to isolate the values you want. Each Filter operator filters according to a specific `"types"` value. After unwinding, there's now a `"types"` value in each row of the array. To determine which "types" value to use in the expression, look at the original `"types"` array. For example, the "`types"` value of `"administrative_area_level_1"` corresponds to the State row of information.

1. Drag and drop two **F****ilter** operators onto the **D****ata Workflow** canvas.
2. Configure the first **F****ilter** operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Filter |
| Label | Filter State |
| Do Note Sanitize Formula | ☐ (**unchecked**) |
| Preserve Argument Type | ☐ (**unchecked**) |
| Expression | types="administrative_area_level_1" |
3. Connect the output port (right) of the **Unwind on types** **U****nwind** operator to the input port (left) of this **Filter State** **F****ilter** operator.
4. Configure the second **F****ilter** operator's **Info** window as follows

| Setting | Value |
| --- | --- |
| Category | Filter |
| Label | Filter Country |
| Do Note Sanitize Formula | ☐ (**unchecked**) |
| Preserve Argument Type | ☐ (**unchecked**) |
| Expression | types="country" |
5. Connect the output port (right) of the **Unwind on types** **U****nwind** operator to the input port (left) of this **Filter Country** **F****ilter** operator.

#### Configure Additional Get Operators

Use two more Get operators to retrieve a specific value from each filtered row. Each row contains both a `"long_name"` and `"short_name"` value. For example, if the State `"long_name"` value is `New York,` then the `"short_name"` is NY. For this example, you'll retrieve the `"short_name"` value for State and Country.

1. Drag and drop two **G****et** operators onto the **D****ata Workflow** canvas.
2. Configure the first **G****et** operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Get |
| Label | Get State short_name |
| Preserve Argument Type | ☐ (**unchecked**) |
| Path | [0].short_name |
3. Connect the upper output port (right) of the **Filter State** **F****ilter** operator to the input port (left) of this **Get State short_name** **G****et** operator.
4. Configure the second **G****et** operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Get |
| Label | Get Country short_name |
| Preserve Argument Type | ☐ (**unchecked**) |
| Path | [0].short_name |
5. Connect the upper output port (right) of the **Filter Country** **F****ilter** operator to the input port (left) of this **Get Country short_name** **G****et** operator.

#### Configure the Console Operators

Add four Console operators to view the outcome of each step in the process. Connect one Console operator to the first Get operator to view the `"address_components"` array before unwinding. Then, connect another to the Unwind operator to view the `"address_components"` array after unwinding. Lastly, connect two Console operators to the second and third Get operators. These display exactly what values the Data Workflow retrieves from the address data object.

> [!NOTE]
> The second and third Get operators only output to Console operators. Use dedicated Output operators when creating applications. Then, you can connect those Output operators to Hidden components to store the final values for reference elsewhere in an application.

1. Drag and drop four **C****onsole** operators onto the **D****ata Workflow** canvas.
2. Configure the first **C****onsole** operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Console |
| Label | Before Unwind |
3. Connect the output port (right) of the **Get address_components array** **G****et** operator to the input port (left) of this**Before Unwind** **C****onsole** operator.
4. Configure the second **C****onsole** operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Console |
| Label | After Unwind |
5. Connect the output port (right) of the **Unwind on types** **U****nwind** operator to the input port (left) of this **After Unwind** **C****onsole** operator.
6. Configure the third **C****onsole** operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Console |
| Label | State short_name |
7. Connect the output port (right) of the **Get State short_name** **G****et** operator to the input port (left) of this **State short_name** **C****onsole** operator.
8. Configure the fourth **C****onsole** operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Console |
| Label | Country short_name |
9. Connect the output port (right) of the **Get Country short_name** **G****et** operator to the input port (left) of this **Country short_name** **C****onsole** operator.
10. Click **Save**.

Here's how the completed Data Workflow looks:

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/dwfUnwindClassic_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A43Z&se=2026-11-07T18%3A57%3A43Z&sr=c&sp=r&sig=M0%2FzFGDZ%2FaRi933THJ6dtwu9op%2FnixPC55BFDaFEPxw%3D)

### Configure the Button Component

Create a button so end-users can click it in Express View and trigger the Data Workflow.

1. Drag and drop a **Button** component onto your canvas, placing it below the **dwfUnwind** **D****ata Workflow** component.
2. In the Property ID, enter **btnRunDWF**.
3. In the Label Text, enter `Run DWF Unwind`.
4. From the **Action Type** drop-down, select **Event**.
5. From the **On Click** drop-down, enter or select **dwfUnwind**.
6. Click **Save & Close**.
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/moduleCompleteClassic_thumb_0_0(3).jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A43Z&se=2026-11-07T18%3A57%3A43Z&sr=c&sp=r&sig=M0%2FzFGDZ%2FaRi933THJ6dtwu9op%2FnixPC55BFDaFEPxw%3D)

**Preview** your module in Express View and open the DevTools Console. Enter an address in the **Address** field and click **Run DWF Unwind**.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/consoleLogs_thumb_0_0(1).jpg?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A43Z&se=2026-11-07T18%3A57%3A43Z&sr=c&sp=r&sig=M0%2FzFGDZ%2FaRi933THJ6dtwu9op%2FnixPC55BFDaFEPxw%3D)

Notice that there are more rows in the **After Unwind** array than in the **Before Unwind** array. Some rows of the original array had two `"types"` values. For example, look at row two of the **Before Unwind** array `"5th Avenue"`. Its `"types"` value is an array with two rows. After unwinding the data, the `"types"` array separates into row two and row three as displayed in the **After Unwind** array.

## How Unwind Works on Different Arrays

This section covers how the Unwind operator works on different types of arrays. Arrays of values are not the only types of arrays. Sometimes, you'll work with an array of objects instead.

You'll also see the effect of setting **Keep Embedding** to either **Yes** or **No**. So, take a moment to explore the following tables and compare and contrast each one.

To understand how Unwind works in different contexts, view the examples below:

### Array with One Value

Use the following sample array:

```json
[
  {
    "keyA": "A",
    "keyB": "B",
    "keyCDE": [
      "CDE"
    ]
  }
]
```

The value of `"keyCDE"` is an array with one value. So, unwind on `keyCDE `to un-nest the array.

This table displays the outcome of unwinding on the `"keyCDE"` key. In the first column, the **Keep Embedding** setting is set to **Yes**. In the second column, it's set to **No**.

| Unwound on keyCDE, Keep Embedding set to Yes |
| --- |
| ```json [ { "keyA": "A", "keyB": "B", "keyCDE": "CDE" } ] ``` |

| Unwound on keyCDE, Keep Embedding set to No |
| --- |
| ```json [ { "0": "C", "1": "D", "2": "E", "keyA": "A", "keyB": "B" } ] ``` |

### Array with Multiple Values

This sample array has multiple values:

```json
[
  {
    "keyA": "A",
    "keyB": "B",
    "keyADG": [
      "ABC",
      "DEF",
      "GHI"
    ]
  }
]
```

The value of `"keyADG"` is a nested array with three values. So, unwind on `keyADG `and check the results in the table below. Like before, the first column displays the effect of setting **Keep Embedding** to **Yes**. The second column displays the outcome of setting **Keep Embedding** to **No**.

| Unwound on keyADG, Keep Embedding set to Yes |
| --- |
| ```json [ { "keyA": "A", "keyB": "B", "keyADG": "ABC" }, { "keyA": "A", "keyB": "B", "keyADG": "DEF" }, { "keyA": "A", "keyB": "B", "keyADG": "GHI" } ] ``` |

| Unwound on keyADG, Keep Embedding set to No |
| --- |
| ```json [ { "0": "A", "1": "B", "2": "C", "keyA": "A", "keyB": "B" }, { "0": "D", "1": "E", "2": "F", "keyA": "A", "keyB": "B" }, { "0": "G", "1": "H", "2": "I", "keyA": "A", "keyB": "B" } ] ``` |

With **Keep Embedding** set to **Yes**, the outcome displays three objects, and each object has a `"keyADG"` key with a different value. Each `"keyADG"` value comes from the original nested array. So, if the original nested array has five values, the outcome displays five objects.

With **Keep Embedding** set to **No**, the outcome displays three objects again. This time, there's no "keyADG" key in each object. Instead, each value from the original nested array gets separated into one of the objects.

### Array of Objects

Now, look at how the Unwind operator works on an array of objects. Here's the sample array:

```json
[
  {
    "keyA": "A",
    "keyB": "B",
    "keyADG": [
      {
        "value": "ABC"
      },
      {
        "value": "DEF"
      },
      {
        "value": "GHI"
      }
    ]
  }
]
```

The value of `"keyADG"` is an array of three objects: `[{"value":"ABC"}, {"value":"DEF"}, {"value":"GHI"}]`. So, see what happens when you unwind on `keyADG`. Like before, the table's left column displays the effect of setting **Keep Embedding** to **Yes**. The right column displays the effect of setting **Keep Embedding** to **No**.

| Unwound on keyADG, Keep Embedding set to Yes |
| --- |
| ```json [ { "keyA": "A", "keyB": "B", "keyADG": { "value": "ABC" } }, { "keyA": "A", "keyB": "B", "keyADG": { "value": "DEF" } }, { "keyA": "A", "keyB": "B", "keyADG": { "value": "GHI" } } ] ``` |

| Unwound on keyADG, Keep Embedding set to No |
| --- |
| ```json [ { "keyA": "A", "keyB": "B", "value": "ABC" }, { "keyA": "A", "keyB": "B", "value": "DEF" }, { "keyA": "A", "keyB": "B", "value": "GHI" } ] ``` |

The outcome displays an array of three objects whether you set **Keep Embedding** to **Yes** or **No**. But, notice how the "keyADG" key disappears when you set **Keep Embedding** to **No**.

When you set **Keep Embedding** to **Yes**, each object displays a `"keyADG"` key/value pair. The value is one of the objects in the original nested array.

When you set **Keep Embedding** to **No**, each object loses the `"keyADG"` key/value pair. Instead, contents of the objects in the original nested array move up a level to replace the `"keyADG"` key/value pair.

## Resources

- [Modify the Unwind operator](/v1/docs/modifying-data-workflow-operators).
- [Introduction to Data Workflow](/v1/docs/introduction-to-data-workflow)
- [Introduction to Data Workflow Operators](/v1/docs/data-workflow-operators)
- [Data Workflow component](/v1/docs/data-workflow-component)
- [Input operator](/v1/docs/input-operator)
- [Output operator](/v1/docs/output-operator)

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

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.

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.

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

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.