---
title: "Build Workday Extract Single Instance Fields — Kiweely"
description: "Build a Workday Extract Single Instance calculated field: source multi-instance field, condition, sort direction, and Instance to be Returned with real…"
url: https://kiweely.com/guides/workday-extract-single-instance-calculated-field
---

# How to Build an Extract Single Instance (ESI) Calculated Field in Workday (With Examples)

Extract Single Instance pulls one related object from a one-to-many multi-instance field by filtering, sorting, then returning the first, last, or nth match. Use it to create a one-to-one hop before Lookup Related Value when you need a scalar from that related object.

-   **Checked** against Workday on November 13
-   Applies to **Workday Calculated Fields**
-   5 min read
-   Published November 13
-   By Kiweely

**Extract Single Instance (ESI)** returns zero or one related object from a multi-instance field that has a one-to-many relationship with the calculated field’s business object. You configure a source multi-instance field, an optional Boolean condition, a required Sort Field and Sort Direction, and which occurrence to return (first, last, or a specific nth). Use ESI when you need the last completed review, the first master’s degree, Dependent #1, or a single enrollment election before promoting a scalar with [Lookup Related Value](https://kiweely.com/guides/workday-lookup-related-value-lrv-calculated-field).

## What Extract Single Instance Does (and Does Not Do)

ESI does not sum, count, concatenate, or return a multi-instance list. It selects **one instance object** (or none). Workday secures creation under the **Custom Field Management** domain in the **System** functional area via **Create Calculated Field**.

Official examples from Workday’s Administrator Guide and Reporting course material include:

-   Current dental, medical, and vision enrollments as separate single-instance fields
-   Dependents as Dependent #1, Dependent #2, and so on
-   Last completed performance review in a given year
-   Last master’s degree received
-   Last time off request
-   Oldest unapproved expense report
-   Last Payroll Result completed

If you need every matching related row, use **Extract Multi-Instance** or keep the multi-instance field on an advanced report related business object instead of ESI.

## How Workday Chooses the Instance at Runtime

Workday Education documents the evaluation order clearly. Treat it as a pipeline, not a spreadsheet `LOOKUP`:

1.  Collect related instances from the **Source Field** (the multi-instance field on the calculated field’s business object).
2.  Apply the **Condition** Boolean against those related instances.
3.  Sort the survivors by **Sort Field** and **Sort Direction**.
4.  Return the configured occurrence: first, last, or a specific nth.

| Configuration Choice | Workday Behavior | Practical Guidance |
| --- | --- | --- |
|  **Source Field** | Multi-instance field ESI filters | Prefer the narrowest delivered multi-instance field that already points at the right object family |
|  **Condition** | Boolean on the related business object | Build a **True/False Condition** field, or use a global Boolean such as **Is True** when every instance is eligible |
|  **Sort Field** | Required sort key | Dates: earliest first on ascending, most recent first on descending. Booleans: false ranks as 0, true as 1 |
|  **Sort Direction** | Ascending or descending | For “most recent,” sort descending by date and return the first occurrence rather than ascending plus last |
|  **Instance to be Returned** | First, last, or nth | Prefer first after an optimized descending sort for performance |

Fails

```
# Anti-pattern: broad source + weak condition + "last" after ascending date sort
Business Object: Worker
Function:        Extract Single Instance
Source Field:    All Benefit Elections (every historical election)
Condition:       Is True
Sort Field:      Election Date
Sort Direction:  Ascending
Instance:        Last occurrence
# Workday still walks every election before picking the last sorted row
```

Works

```
# Narrow source + targeted condition + descending + first
Business Object: Worker
Function:        Extract Single Instance
Source Field:    Benefit Elections (or the most specific multi-instance available)
Condition:       CF_TF_Medical_Election_Active (True/False Condition on election type/status)
Sort Field:      Election Date
Sort Direction:  Descending
Instance:        First occurrence
# Returns the newest matching medical election, or blank if none match
```

Condition and Sort Field are not optional in practice

If you truly need every instance considered, Workday Education still expects a Condition (for example global **Is True**) and a Sort Field (for example global **Any Field** when the condition already isolates one row). Leaving those prompts empty blocks a valid definition.

## Pair ESI with Lookup Related Value for Scalars and Filters

ESI returns an **instance**. Reports can show that instance as a column, but grouping, totaling, matrix axes, and many business process condition rules need a field **on** that instance promoted to the primary business object. That is the standard ESI then LRV chain:

1.  Create ESI on **Worker** to return the single **Performance Review** instance you care about.
2.  Create **Lookup Related Value** with Lookup Field = that ESI and Return Value = **Overall Rating** (or another field on Performance Review).
3.  Use the LRV field for filters, sorts, summarization, or condition rules on Worker.

Without ESI, LRV cannot hop a one-to-many multi-instance field because Workday requires a one-to-one relationship for Lookup Related Value. Confirm cardinality with the **Business Object Details** report before you build the chain. For broader function selection, see [Workday calculated field types and examples](https://kiweely.com/guides/workday-calculated-field-types-examples).

## Common Blank Results and How to Prove the Fix

Blank ESI output is usually configuration, not a platform defect. Diagnose in this order:

| Symptom | Likely Cause | What to Check |
| --- | --- | --- |
| Always blank | Condition never true | Test the Boolean alone as a report column on the related object path |
| Blank for some workers only | No related rows match | Confirm those workers actually have the multi-instance data as of the report effective date |
| Wrong instance returned | Sort Direction or Instance to be Returned inverted | Compare ascending/descending and first vs last on a known worker with three dated rows |
| Downstream LRV blank | ESI blank, or wrong Return Value object | Open **View Calculated Field** / **Calculated Field Usage Hierarchy** and walk the chain |

Security still applies at runtime. If the running user cannot see the related instances, ESI behaves as if those instances were absent. Use **View Security for Securable Item** on the source multi-instance field when two users get different ESI results on the same worker. For blank calculated fields more generally, see [why a calculated field returns blank](https://kiweely.com/guides/calculated-field-returns-blank).

## Build, Audit, and Verify in the Tenant

1.  Open **Create Calculated Field**, choose the business object (for example **Worker**), and select Function **Extract Single Instance**.
2.  Set **Source Field**, **Condition**, **Sort Field**, **Sort Direction**, and **Instance to be Returned**.
3.  Optionally mark helper Booleans as **Intermediate Calculation** on Additional Info so they stay searchable without cluttering report field prompts.
4.  Run **Calculated Field Exception Audit** (or **Report Specific Calculated Field Exception Audit** for report-scoped fields) after save.
5.  Validate with a side-by-side advanced report: related multi-instance column vs ESI vs LRV scalar across workers with zero, one, and many matches.

If you want to design the ESI condition and sort order against live tenant relationships without clicking through every related object prompt by hand, [Kiweely Vine](https://kiweely.com/vine) can read the business object graph from your connected tenant and draft the ESI definition for you to approve before anything changes. Vine Free is free for your Workday personal developer account and its tenant. Any other tenant needs Vine Personal at $99 a month for one person, or a Vine Team seat at $149 a month.

## Frequently asked questions

### Does Extract Single Instance always return one instance?

No. Workday returns either zero instances or one instance. If the Boolean condition matches nothing on the source multi-instance field, the ESI result is blank, and any Lookup Related Value stacked on that ESI also returns blank.

### What Sort Field should I use when every qualifying instance is equally valid?

Sort Field is required. When you do not need a meaningful sort because the condition already narrows to one instance, Workday Education guidance is to use a global field such as Any Field so the definition can save and still return that single match.

### Why do I need Extract Single Instance before Lookup Related Value?

Lookup Related Value requires a one-to-one relationship. Extract Single Instance converts a one-to-many multi-instance field into a single-instance hop so Lookup Related Value can promote a field from that related object onto the primary business object.

### How do I prove an Extract Single Instance field is correct in the tenant?

Place the ESI field and a temporary related-business-object column from the same source on a small advanced custom report, filter to known workers with zero, one, and many matching related rows, and confirm the ESI returns the expected instance or blank for each case.

## Sources checked

-   [Extract Single Instance](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/calculated-fields/calculated-field-functions/dan1370797398759.html)
-   [Lookup Related Value](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/calculated-fields/calculated-field-functions/dan1370796324282.html)
-   [Create Calculated Fields](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/calculated-fields/bxe1470157762583.html)
-   [Configure Calculated Fields with True/False Condition](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/calculated-fields/calculated-field-functions/dan1370796333964.html)
-   [Calculated Fields (Workday Education)](https://doc.workday.com/workday-education/en-us/course-manuals/workday-reporting/calculated-fields.html)

## Related guides

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

-   [### How to Sum or Count Multi-Instance Rows in Workday Using Aggregate Related Instances (ARI) Workday Aggregate Related Instances does not add numbers or count rows: it collects unique related objects across a relationship into one deduplicated multi-instance list. Pair ARI with Sum Related Instances, Count Related Instances, and Arithmetic Calculation for numeric rollups.](https://kiweely.com/guides/workday-aggregate-related-instances-ari-sum-count)
-   [### Workday Lookup Related Value (LRV) Explained: Crossing Business Objects Without Blank Rows Lookup Related Value promotes a field from a related business object onto the primary business object when the relationship is one-to-one. That promotion lets you filter, group, sort, summarize, and build condition rules without exploding the report into blank multi-instance rows.](https://kiweely.com/guides/workday-lookup-related-value-lrv-calculated-field)
-   [### Workday Calculated Fields: How to Build Them and Fix Common Errors Choose the business object and scope, configure three core functions, and fix missing fields, empty results and incorrect conditions. Examples use Workday’s documented fields and options.](https://kiweely.com/guides/workday-calculated-fields)
-   [### Workday calculated fields tutorial: every function type with a worked example, including extract single instance Create a calculated field with the Create Calculated Field task: pick the business object, then a function. This tutorial gives one worked example for each function family, including extract single instance.](https://kiweely.com/guides/workday-calculated-field-types-examples)
-   [### Why does my Workday calculated field return blank in a report? A calculated field returns blank when its function finds nothing to return, when its business object is not reachable from the report, or when the viewer cannot see a field it reads. Test one known instance first.](https://kiweely.com/guides/calculated-field-returns-blank)

### More guides on Reports and calculated fields

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

-   [Workday Date Calculated Fields: Increment or Decrement Date and Date Difference](https://kiweely.com/guides/workday-calculated-field-date-difference-increment)
-   [How do I group, aggregate and drill down in Workday advanced, matrix and composite reports?](https://kiweely.com/guides/workday-matrix-reports-aggregations-drilldowns)
-   [Why does a shared Workday report show blank columns or fewer rows to another user?](https://kiweely.com/guides/workday-custom-report-sharing-security-empty)
-   [Slow Workday Custom Reports: Fixing Data Source Filter and Calculated Field Timeouts](https://kiweely.com/guides/workday-slow-custom-report-performance-tuning)
-   [Workday composite reports: fix Map Fields For Join errors, prompt sets and subreport problems](https://kiweely.com/guides/workday-composite-report-errors)
-   [Why a Workday user can’t see a field, report, or task](https://kiweely.com/guides/workday-user-cannot-see-field-task)
-   [Why a Workday report returns no rows, or the wrong rows](https://kiweely.com/guides/workday-report-no-rows)
-   [Why a Workday calculated field is missing from the report field picker](https://kiweely.com/guides/why-workday-calculated-field-missing-from-picker)

### From the blog on Reports and calculated fields

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

-   [Approving Workday Expense Reports and Purchase Requisitions in Teams and Slack](https://kiweely.com/blog/workday-expense-report-and-requisition-approvals-in-teams-slack)
-   [Untangling a 14-Subreport Workday Composite Report Nobody on Your Team Built](https://kiweely.com/blog/reverse-engineering-inherited-workday-composite-reports)
-   [How Consultants Catch Silent Report and Browser Regressions After a Workday Semiannual Release](https://kiweely.com/blog/regression-testing-workday-ui-and-timezone-changes)

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