---
title: "Omit Operator"
slug: "omit-operator"
description: "Learn how to use the Omit operator to remove sensitive data points from your data set, enhancing security and efficiency in your Data Workflow."
updated: 2025-11-11T17:52:47Z
published: 2025-11-12T14:27:26Z
canonical: "docs.unqork.io/omit-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.

# Omit Operator

UDesignerClassic Designer

![Settings panel displaying options for omitting categories and labels in a user interface.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(274).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A10Z&se=2026-11-09T04%3A51%3A10Z&sr=c&sp=r&sig=8j7BE%2B56EOC5P4NGgHp3r7K5MumqSWDW5iz5s3FxM60%3D)The **Omit operator** lets you easily remove specific data points from a data set. First, you’ll reference keys in the operator's Info window. Then, the operator removes the keys you've entered (and their values) from any data passed.

To better understand how the operator works, it's important to understand how data is stored in an array. In a data table, a key refers to a single column. So, if you have a data set of sensitive end-user identification numbers, you might have a column with the key `id`. You can configure the Omit operator to remove this column if that information to avoid security issues downstream processes. Removing irrelevant data from downstream processes can also help improve an application's efficiency.

You might also be merging data in your Data Workflow. If that's the case, you might have duplicate merge indexes in your final data that you can easily remove using an Omit operator.

> [!NOTE]
> The Omit operator does not delete the data from your original data set. The Omit operator only excludes data as it passes through your Data Workflow.

You’ll find the Omit operator under the Table group at the left of the Data Workflow canvas.

## About the Info Window

Here's a breakdown of each setting in the 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. |
| Omit Keys | Enter the key for any data you want the operator to remove. When working with a data table, the key is the column name. You can remove more than one key using a single Omit operator. Separate each new key in this field by a comma. You can also set your Omit Keys using an argument. To do that, connect an Input operator to the operator's argument port. Then, enter` _arg` in this field. Remember that the value passed using an argument must still match a key in your data set. |

## Adding an Omit Operator

In this example, you'll learn how to exclude sensitive information from the output of your Data Workflow. After creating a data table that stores account information, you'll set the operator's key to remove all account key/value information from the output.

### Configure the Data Table Component

First, let's set up your list of account details using a [Data Table](/v1/docs/data-table-component) component.

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

| # | firstName | accountValue | accountNumber | appStatus |
| --- | --- | --- | --- | --- |
| 1 | Blair | 543891 | 12345 |  |
| 2 | JJ | 1000000 | 12346 |  |
| 3 | Jim | 1000000 | 12347 |  |
| 4 | Evan | 7432572 | 12348 |  |
| 5 | Charlotte | 5000000 | 12349 |  |
| 6 | Amy | 5439294 | 12350 |  |
| 7 | Brian | 17890 | 12351 |  |
| 8 | Rupert | 19578 | 12352 |  |
| 9 | Emily | 54389 | 12353 |  |

![Data table displaying account information including names, values, numbers, and statuses.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(276).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A10Z&se=2026-11-09T04%3A51%3A10Z&sr=c&sp=r&sig=8j7BE%2B56EOC5P4NGgHp3r7K5MumqSWDW5iz5s3FxM60%3D)
4. Click **Save Component**.

### Configure the Data Workflow Component

Now, let's set up your [Data Workflow](/v1/docs/data-workflow) component. You'll configure your Omit operator to remove two of the original columns.

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

#### Configure the Input Operator

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

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

#### Configure the Omit Operator

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

| Setting | Value |
| --- | --- |
| Category | Omit |
| Label | Omit Status and Value |
| Preserve Argument Type | ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/icon_unchecked(1).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A10Z&se=2026-11-09T04%3A51%3A10Z&sr=c&sp=r&sig=8j7BE%2B56EOC5P4NGgHp3r7K5MumqSWDW5iz5s3FxM60%3D) (unchecked |
| Omit Keys | appStatus,accountValue |
3. Connect the output port (right) of the `dtAccounts` **Input** operator to the input port (left) of the `Omit Status and Value` **Omit** operator.

#### Configure the Console Operator

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 | Omitted Keys |
3. Connect the output port (right) of the `Omit Status and Value` **Omit** operator to the input port (left) of the `Omitted Keys` **Console** operator.

![Workflow diagram showing data omission process with input and console elements.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(277).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A10Z&se=2026-11-09T04%3A51%3A10Z&sr=c&sp=r&sig=8j7BE%2B56EOC5P4NGgHp3r7K5MumqSWDW5iz5s3FxM60%3D)
4. Click **Save Component**.

### Configure the Button Component

Lastly, add a [Button](/v1/docs/button-component#resources) component to trigger your Data Workflow component.

1. Drag and drop a **Button** component onto your canvas, placing it below your Data Workflow component.
2. In the **Property ID** field, enter `btnOmitKeys`.
3. In the **Label** **Text** field, enter `Omit Keys`.
4. From the **Action Type** drop-down, select **Event.**
5. In the **Trigger on Click** field, enter `dwfOmitKeys`.

![Button configuration showing action type and triggers for omitting keys event.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(278).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A10Z&se=2026-11-09T04%3A51%3A10Z&sr=c&sp=r&sig=8j7BE%2B56EOC5P4NGgHp3r7K5MumqSWDW5iz5s3FxM60%3D)
6. Click **Save Component**.
7. **Save** your module.

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

![Settings interface showing dtAccounts and dwfOmitKeys options with an omit keys button.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(279).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A10Z&se=2026-11-09T04%3A51%3A10Z&sr=c&sp=r&sig=8j7BE%2B56EOC5P4NGgHp3r7K5MumqSWDW5iz5s3FxM60%3D)

Preview your module in Express View and open the DevTools Console. Now, click the **Omit Keys** button. In your `Omitted Keys` **Console**, you'll see all columns from your data table except **appStatus** and **accountValue**.

![Console output showing omitted keys and account details for various users.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Dwf_OmitOperator_Express(1).jpg?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A10Z&se=2026-11-09T04%3A51%3A10Z&sr=c&sp=r&sig=8j7BE%2B56EOC5P4NGgHp3r7K5MumqSWDW5iz5s3FxM60%3D)

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Dwf_OmitOperator_Operator.jpg?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A10Z&se=2026-11-09T04%3A51%3A10Z&sr=c&sp=r&sig=8j7BE%2B56EOC5P4NGgHp3r7K5MumqSWDW5iz5s3FxM60%3D)The **Omit operator** lets you easily remove specific data points from a data set. First, you’ll reference keys in the operator's Info window. Then, the operator removes the keys you've entered (and their values) from any data passed.

To better understand how the operator works, it's important to understand how data is stored in an array. In a data table, a key refers to a single column. So, if you have a data set of sensitive end-user identification numbers, you might have a column with the key `id`. You can configure the Omit operator to remove this column if that information to avoid security issues downstream processes. Removing irrelevant data from downstream processes can also help improve an application's efficiency.

You might also be merging data in your Data Workflow. If that's the case, you might have duplicate merge indexes in your final data that you can easily remove using an Omit operator.

> [!NOTE]
> The Omit operator does not delete the data from your original data set. It only excludes data as it passes through your Data Workflow.

You’ll find the Omit operator under the [Table](/v1/docs/table-operators) group to the left of the [Data Workflow](/v1/docs/data-workflow-component) canvas.

## About the Info Window

Here's a breakdown of each setting in the 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. |
| Omit Keys | Enter the key for any data you want the operator to remove. When working with a data table, the key is the column name. You can remove more than one key using a single Omit operator. Separate each new key in this field by a comma. You can also set your Omit Keys using an argument. To do that, connect an Input operator to the operator's argument port. Then, enter` _arg` in this field. Remember that the value passed using an argument must still match a key in your data set. |

## Adding an Omit Operator

In this example, you'll learn how to exclude sensitive information from the output of your Data Workflow. After creating a data table that stores account information, you'll set the operator's key to remove all account key/value information from the output.

### Configure the Data Table Component

First, let's set up your list of account details using a [Data Table](/v1/docs/data-table-component) component.

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

| # | firstName | accountValue | accountNumber | appStatus |
| --- | --- | --- | --- | --- |
| 1 | Blair | 543891 | 12345 |  |
| 2 | JJ | 1000000 | 12346 |  |
| 3 | Jim | 1000000 | 12347 |  |
| 4 | Evan | 7432572 | 12348 |  |
| 5 | Charlotte | 5000000 | 12349 |  |
| 6 | Amy | 5439294 | 12350 |  |
| 7 | Brian | 17890 | 12351 |  |
| 8 | Rupert | 19578 | 12352 |  |
| 9 | Emily | 54389 | 12353 |  |

![Data table displaying account information including names, values, numbers, and statuses.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Dwf_OmitOperator_Dt.jpg?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A10Z&se=2026-11-09T04%3A51%3A10Z&sr=c&sp=r&sig=8j7BE%2B56EOC5P4NGgHp3r7K5MumqSWDW5iz5s3FxM60%3D)
4. Click **Save**.

### Configure the Data Workflow Component

Now, let's set up your [Data Workflow](/v1/docs/data-workflow) component. You'll configure your Omit operator to remove two of the original columns.

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

#### Configure the Input Operator

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

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

#### Configure the Omit Operator

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

| Setting | Value |
| --- | --- |
| Category | Omit |
| Label | Omit Status and Value |
| Preserve Argument Type | ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/icon_unchecked(1).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A10Z&se=2026-11-09T04%3A51%3A10Z&sr=c&sp=r&sig=8j7BE%2B56EOC5P4NGgHp3r7K5MumqSWDW5iz5s3FxM60%3D) (unchecked |
| Omit Keys | appStatus,accountValue |
3. Connect the output port (right) of the `dtAccounts` **Input** operator to the input port (left) of the `Omit Status and Value` **Omit** operator.

#### Configure the Console Operator

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 | Omitted Keys |
3. Connect the output port (right) of the `Omit Status and Value` **Omit** operator to the input port (left) of the `Omitted Keys` **Console** operator.

![Data workflow options for omitting keys in a data processing interface.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Dwf_OmitOperator_Dwf.jpg?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A10Z&se=2026-11-09T04%3A51%3A10Z&sr=c&sp=r&sig=8j7BE%2B56EOC5P4NGgHp3r7K5MumqSWDW5iz5s3FxM60%3D)
4. Click **Save**.

### Configure the Button Component

Lastly, add a [Button](/v1/docs/button-component#resources) component to trigger your Data Workflow.

1. Drag and drop a **Button** component onto your canvas, placing it below your Data Workflow.
2. In the **Property ID** field, enter `btnOmitKeys`.
3. In the **Label** **Text** field, enter `Omit Keys`.
4. Under **Action Type**, select **Event.**
5. In the **Trigger on Click** field, enter `dwfOmitKeys`.

![Button configuration for omitting keys with action triggers and save options displayed.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(273).png?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A10Z&se=2026-11-09T04%3A51%3A10Z&sr=c&sp=r&sig=8j7BE%2B56EOC5P4NGgHp3r7K5MumqSWDW5iz5s3FxM60%3D)
6. Click **Save & Close**.
7. **Save** your module.

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

![Module editor interface displaying components and frequently used options for editing.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Dwf_OmitOperator_ME.jpg?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A10Z&se=2026-11-09T04%3A51%3A10Z&sr=c&sp=r&sig=8j7BE%2B56EOC5P4NGgHp3r7K5MumqSWDW5iz5s3FxM60%3D)

Preview your module in Express View and open the DevTools Console. Now, click the **Omit Keys** button. In your `Omitted Keys` **Console**, you'll see all columns from your data table except **appStatus** and **accountValue**.

![Console output showing omitted keys and account details for various users.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Dwf_OmitOperator_Express(1).jpg?sv=2026-02-06&spr=https&st=2026-11-09T03%3A51%3A10Z&se=2026-11-09T04%3A51%3A10Z&sr=c&sp=r&sig=8j7BE%2B56EOC5P4NGgHp3r7K5MumqSWDW5iz5s3FxM60%3D)

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

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.

In Unqork an application is a program used to perform specific tasks. An application can be one of two types: workflow or module.

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.

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 Unqork front-end application framework that delivers Creator-built applications to end-users. Express is the layer end-users interact with—the published forms, screens, and navigation built in the Module Builder. Express is distinct from Express View, which is a Creator-facing preview tool in the IDE.

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

## Related

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