---
title: "Clear Workday Extend BO Fields in Inbound EIB with {empty}"
description: "Clear text fields and nullify single or multi-instance references on Workday Extend Business Objects in Inbound EIB spreadsheets using exact {empty} tags."
url: https://kiweely.com/guides/workday-extend-eib-clear-text-nullify-fields-empty-tag
---

# How to Blank Out Text Fields and Nullify Reference Values on Workday Extend Business Objects via Inbound EIB Using {empty}

Leaving a spreadsheet cell blank or entering “” or null in an Inbound EIB does not clear existing field values on a Workday Extend Business Object. Learn how to use the {empty} tag, avoid the leading/trailing whitespace trap in Excel, and remove specific multi-instance values.

-   **Checked** against Workday on November 6
-   Applies to **Workday Extend**
-   4 min read
-   Published November 6
-   By Kiweely

## Why Blank Cells, `""`, and `null` Do Not Clear Extend Business Object Fields in an EIB

When updating existing Workday Extend Model Business Object (MCBO) records via an Inbound Enterprise Interface Builder (EIB) spreadsheet (`Extend Spreadsheet Template`), leaving a cell empty tells Workday to **ignore that field and preserve the existing value** on the Business Object instance. Conversely, typing `""`, `" "`, or `null` into a `TEXT` cell is either treated as a literal string (setting the text field to the literal characters `null` or `""`) or rejected during validation.

To instruct the Workday Extend EIB processor to overwrite an existing `TEXT` value or reference field with an empty/null state, you must enter the exact Workday EIB directive **`{empty}`** in the spreadsheet cell.

| Value Entered in `.xlsx` Cell | Resulting Behavior on Extend Business Object |
| --- | --- |
|  *(Blank / empty cell)* | Preserves the existing field value untouched |
| `""` or `null` | Writes literal characters `""` or `null` into a `TEXT` field (or fails reference lookup) |
| `" {empty}"` or `"{empty} "` | Fails to clear the field or throws a validation error due to leading/trailing space |
|  **`{empty}`** |  **Clears the field back to blank / null** |

## The Leading and Trailing Whitespace Trap in Excel (`" {empty}"`)

The single most common reason `{empty}` fails to clear a field—or triggers an unexpected EIB validation error—is an invisible **leading or trailing space** inside the Excel cell (for example, `" {empty}"` or `"{empty} "` introduced when copying and pasting from an email, chat window, or web page).

When the Extend EIB parser reads `" {empty}"` with a leading space:

-   On a **`TEXT` field**, it does not match the `{empty}` token and either leaves the old value intact or writes the literal string `" {empty}"`.
-   On a **`SINGLE_INSTANCE` or `MULTI_INSTANCE` reference field**, it attempts to resolve `" {empty}"` as a Workday ID (`WID`) or Reference ID and fails the row with a `not found (code: S21)` validation error.

Before saving and uploading your `.xlsx` template in **Launch / Schedule Integration**, run an Excel Find & Replace or formula check (`=LEN(cell)` should equal `7` for `{empty}`) to strip any leading or trailing spaces around `{empty}`.

## Clearing Text Fields vs. Nullifying Single-Instance and Multi-Instance Fields

### 1\. Blanking Out a `TEXT` Field on an Existing Record

1.  Run an Outbound EIB (or **View WQL Query Result**) to export the `Workday ID` (`id`) of the Extend Business Object records you need to update.
2.  In your generated Inbound EIB `.xlsx` spreadsheet template (created via **Template Model** > **Generate Spreadsheet Template**), populate the **ID** column with the record’s 32-character `Workday ID`.
3.  In the column corresponding to the `TEXT` field you want to clear (for example, `Comments` or `Legacy Reference Code`), enter exact **`{empty}`** with no spaces.
4.  Leave all other columns on that row blank if you want their existing values preserved.

### 2\. Clearing a `SINGLE_INSTANCE` Reference Field

To clear a single-instance relationship field (whether it targets another Extend Business Object or a Workday-delivered Business Object such as `Worker` or `Cost_Center`), enter **`{empty}`** in the column for that relationship field alongside the record’s `Workday ID`.

### 3\. Removing a Specific Value from a `MULTI_INSTANCE` Field (`functionalArea`)

In an Extend Inbound EIB spreadsheet, a `MULTI_INSTANCE` relationship field (for example, `functionalArea` containing multiple related instances on a single parent Business Object record) spans multiple sub-rows or multi-instance columns keyed to the parent record’s `Spreadsheet Key` / `ID`:

-   **To clear the entire `MULTI_INSTANCE` collection** on a record, enter **`{empty}`** in the multi-instance field cell for that record.
-   **To remove one specific WID (`xyz`) from a `MULTI_INSTANCE` field while keeping the remaining values**: Because an Inbound EIB update on a multi-instance collection replaces the collection for the rows supplied in the template, either:
    1.  Place **`{empty}`** on the specific target cell/row to nullify that entry when the template column maps to a single slot, OR
    2.  Supply the parent record’s `ID` along with only the **retained** `WID` rows in the multi-instance column (omitting the `WID` you want removed) so the EIB replaces the multi-instance list with the retained set.

## Required Security Permissions for Extend Inbound EIBs

If the user launching the EIB receives a permission error even when `{empty}` is formatted properly, verify that the Extend app’s security domain grants **Modify** permission to the user’s security group:

1.  Open the **App Manager** report in your Workday tenant and click **Configure** next to your Extend App.
2.  Under **Model Components** > **Security Domains**, select **Edit Domain Security Policy Permissions** from the related actions menu of the security domain securing your Business Object.
3.  Under **Report/Task Permissions**, add the security group of the EIB operator and check **Modify** (and **View**).
4.  Run **Activate Pending Security Policy Changes**.

## How to Verify in the Tenant

1.  Generate a fresh `.xlsx` template from your Inbound EIB via **Template Model** > **Generate Spreadsheet Template**.
2.  Populate one test row with an existing Extend Business Object `Workday ID` and type **`{empty}`** (verifying `=LEN()` is exactly `7`) into the target `TEXT` or reference column.
3.  Launch the EIB via **Integration** > **Launch / Schedule**, upload the `.xlsx` file, and enable **Validate Only Load** first to confirm 0 errors on the **Messages** tab.
4.  Re-run the EIB with **Validate Only Load** unchecked and query the record in **View WQL Query Result** (or open its PMD View page) to confirm the field is now completely blank.

## Sources checked

-   [Load Data to Extend Business Objects Using EIBs](https://developer.workday.com/documentation/GUID-fa252f19-a2d0-449c-9313-705f3e14196b-enHYPHENus)
-   [Configure Extend Apps to Manage Data Using EIBs](https://developer.workday.com/documentation/GUID-48a53305-19de-4b70-92d8-2f28cd94a222-enHYPHENus)
-   [Extract Data from Extend Business Objects Using EIBs](https://developer.workday.com/documentation/GUID-bb9aa5c0-b58b-41a9-96bd-cd1c1af495ca-enHYPHENus)
-   [Concept: EIB Spreadsheet Data Entry Guidelines](https://doc.workday.com/admin-guide/en-us/integrations/enterprise-interface-builder-eib-/inbound-eibs/dan1370796370630.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Resolving “Tenant mapping not found (OP-4008)”, EU vs. US Regional Base URL 401 Errors, and client\_secret\_basic in Workday Extend OAuth 2.0 Connecting an external system to Workday Extend APIs via OAuth 2.0 Client Credentials can fail with OP-4008 (Tenant mapping not found) or 401 Unauthorized. Learn how to configure Create Client Credentials Mapping, select the right regional API Gateway URL, and enforce client\_secret\_basic.](https://kiweely.com/guides/workday-extend-oauth-tenant-mapping-op-4008-eu-base-url-client-secret-basic)
-   [### Working Around the 10-Relationship Limit on a Workday Extend Model Business Object (MCBO) Using a Helper Object Workday Extend enforces a platform ceiling of 10 SINGLE\_INSTANCE and MULTI\_INSTANCE relationship fields per Model Business Object (MCBO) and 25 delivered target relationships per app. Learn how to reserve the 10th slot for a 1:1 helper extension object and query across both objects in WQL.](https://kiweely.com/guides/workday-extend-mcbo-10-single-instance-relationship-limit-helper-bo)
-   [### Fixing “Object instance has properties which are not allowed by the schema (parentBusinessProcesses, initiationPageRoute)” on Extend Subprocesses Adding an Extend Model Business Process as a subprocess of a delivered Workday business process fails validation if parentBusinessProcesses and initiationPageRoute are placed at the root of the .bp file or omit the {eventStepId} parameter. Learn the complete .bp, .amd, and .pmd configuration.](https://kiweely.com/guides/workday-extend-bp-subprocess-allowedparentprocesses-eventstepid)

### More guides on Extend apps and pages

[All 97 guides](https://kiweely.com/guides#extend)

-   [Cascading dropdowns and instance lists in Workday Extend](https://kiweely.com/guides/workday-extend-cascading-instance-lists)
-   [How to move Workday Extend apps to a new developer tenant before the old one expires or is deleted](https://kiweely.com/guides/workday-extend-move-apps-new-developer-tenant)
-   [Why a Workday Graph API query suddenly fails with “Cannot query field”](https://kiweely.com/guides/workday-graphql-cannot-query-field)
-   [How to build a worker search prompt in a Workday Extend page](https://kiweely.com/guides/workday-extend-worker-search)
-   [Which Workday Extend widget to use for what](https://kiweely.com/guides/workday-extend-widget-guide)
-   [Workday Extend Professional is now Extend AI: Core vs AI vs legacy limits, storage and AI features](https://kiweely.com/guides/workday-extend-legacy-vs-extend-professional)
-   [Model business processes in Workday Extend: how a transaction gets created and approved](https://kiweely.com/guides/workday-extend-model-business-process)
-   [Version control for Workday Extend apps: GitHub, Local Disk Sync and automated deploys](https://kiweely.com/guides/workday-extend-version-control-github)

### From the blog on Extend apps and pages

[All posts](https://kiweely.com/blog)

-   [Debugging Workday Extend web services: Postman vs. kiweely](https://kiweely.com/blog/debugging-workday-extend-web-services-postman-vs-kiweely)
-   [Rapid ideation and prototyping of Workday Extend apps](https://kiweely.com/blog/rapid-prototyping-workday-extend-apps-with-kiweely)
-   [Claude Code for Workday Extend: what changes when it can reach your tenant?](https://kiweely.com/blog/claude-code-workday-extend-tenant)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
