Every Workday calculated field starts with two fixed choices in the Create Calculated Field task (secured by the Custom Field Management domain in the System functional area): the Business Object the field lives on and the Function that computes its value. Picking the wrong function—or building it on the wrong Primary Business Object (PBO)—is why fields fail to appear in report prompts, cannot be selected in a matrix report, or return blank at runtime.
This reference explains the four official Workday calculated field families, how to chain True/False Condition, Extract Single Instance (ESI), Lookup Related Value (LRV), and Evaluate Expression, and which functions are supported on Prism Analytics data sources.
1. Retrieve Your Data functions (the relationship builders)
Most multi-step Workday calculated fields combine functions from the retrieval family to walk from the report's Primary Business Object to a field on a Related Business Object (RBO):
| Function | Input relationship | Output type | When to use it |
|---|---|---|---|
| Lookup Related Value (LRV) | Strictly 1:1 (a single-instance or self-referencing Lookup Field) | The data type of the selected Return Value field | Promote a field from an RBO onto the PBO so you can filter, group, sort, summarize, use it on a matrix report (which restricts fields to the PBO), or reference it in a business process condition rule. |
| Extract Single Instance (ESI) | 1:Many (a multi-instance related object field) | Single Instance | Pull exactly one instance (first, last, most recent, or matching a sort and condition rule) out of a multi-instance field—such as a worker's current medical election, last completed performance review, or primary dependent. |
| Extract Multi-Instance (EMI) | 1:Many (one or two multi-instance fields) | Multi-Instance | Filter a multi-instance collection by a boolean condition—or compute the union, intersection, or exclusion of two multi-instance fields—such as all staffing events in the last 12 months. |
| Aggregate Related Instances | 1:Many across a related object | Multi-Instance | Roll up all instances associated with a source field across a related object, such as all job profiles across every position in a supervisory organization. |
| True/False Condition | Fields on the same business object | Boolean (True / False) |
Define the filter criteria required by ESI, EMI, Evaluate Expression, Sum Related Instances, Count Related Instances, or business process condition rules. |
| Evaluate Expression | Ordered list of True/False conditions |
Text, Numeric, Date, Currency, or Single Instance | Return a different default or calculated value for the first boolean condition that evaluates to True (an IF / ELSE IF / ELSE switch), such as mapping length of service into seniority tiers. |
| Evaluate Expression Band | Boolean conditions mapped to bands | Grouped Instance | Group records into named bands—such as Junior, Midlevel, and Senior—for reporting and summarization. |
| Lookup Value as of Date | Any field on the business object + effective date | Field's underlying type | Inspect a field's value as of a specific effective date (for example, annual salary at prior year-end or value 1 millisecond before an event). |
| Lookup Hierarchy / Lookup Hierarchy Rollup | Hierarchical object (Supervisory Org, Cost Center, Spend Category) | Single Instance / Rollup | Pull a specific management or hierarchy level, or roll up report data starting at the top node of an organization hierarchy. |
| Lookup Organization / Lookup Organizational Roles | Employee, Worker, or Organization business object | Organization node / Role assignees | Identify a worker's department or organization level, or return the worker assigned to a role such as Expenses Representative or Facilities Manager. |
| Lookup Range Band / Lookup Date Rollup | Numeric value or Date field | Band / Period rollup | Bucket numeric values into configured ranges (such as Highly Compensated), or map a date into a fiscal year-quarter (2026-Q1) or week-end date for composite report repeating column groups. |
| Lookup Field with Prompts / Lookup Translated Value | Delivered field with built-in prompts / Text field | Prompted value / Translated text | Supply prompt values to a Workday-delivered prompted field, or return a text field's value in a specified target language. |
| Substring Text | Text or Single Instance field | Text | Extract characters before/after a delimiter or by starting character position and fixed length. |
The core chaining pattern: TF → ESI → LRV
Because Lookup Related Value requires a one-to-one relationship between the PBO and the RBO, you cannot point an LRV directly at a multi-instance collection like Dependents, Education, or Benefit Elections. Instead, build the chain bottom-up:
- Step 1 — True/False Condition (
TF) on the Related Business Object: Create a True/False Condition on the target RBO (for example, Benefit Election) that identifies the exact row you want (such asCoverage Type = MedicalandCurrently Active = True). - Step 2 — Extract Single Instance (
ESI) on the Primary Business Object: Create an ESI on the PBO (such as Worker), select the multi-instance field (Current Benefit Elections), apply theTFcondition from Step 1, and choose the sort field and direction (First or Last occurrence) so Workday returns a single instance. - Step 3 — Lookup Related Value (
LRV) on the Primary Business Object: Create an LRV on the PBO, select theESIfrom Step 2 as the Lookup Field (which is now a 1:1 single instance), and select the specific attribute you want to display or filter on (such as Benefit Plan or Employee Cost) as the Return Value.
When configuring an LRV, check the Use Return Value Field Formatting option on the Additional Info tab if you want Workday to preserve the return field's date precision, alternate display ID, numeric rounding, or rich text formatting. Note that Workday retains this formatting in the browser and in PDF or XML exports, but does not retain it when exporting to Microsoft Excel.
2. Perform Calculations on Your Data (math, counts, and dates)
Mathematical calculated fields follow standard PEMDAS order of operations (Parentheses, Exponents, Multiplication, Division, Addition, Subtraction):
- Arithmetic Calculation: Adds, subtracts, multiplies, or divides numeric or currency fields (such as computing a bonus percentage of base salary or daily rate).
- Sum Related Instances & Count Related Instances: Sums a numeric field or counts instances across a 1:Many related business object filtered by a condition (for example, summing taxable invoice lines for VAT or counting open positions in a supervisory organization).
- Date Difference: Computes the number of days, months, or years between two dates (such as worker age or days since a position opened).
- Increment or Decrement Date: Adds or subtracts years, months, days, hours, minutes, seconds, or milliseconds from a date field. A classic audit pattern subtracts 1 millisecond from a business process event's effective timestamp and feeds that calculated timestamp into a Lookup Value as of Date field to compare the value of a field immediately before the event ran against its value after the event.
- Text Length: Returns the character count (including spaces) of a text or single-instance field, commonly used in validation rules to enforce downstream integration field limits (such as a 15-character city name cap).
3. Change Your Data into Different Formats & Configure Constants
When building integration extracts, notifications, or composite report keys, combine formatting functions with typed constants:
- Formatting functions: Concatenate Text (joins text and fields into a single string), Format Date (extracts fiscal year, period, month, or day as text), Format Number (applies locale decimal separators, currency symbols, or fixed precision as text), Format Text (converts to upper, lower, or proper case and strips or replaces delimiters), Convert Text to Number (casts numeric text for math operations), and Convert Currency (converts amounts to a target currency using an effective exchange rate type and date).
- Constant functions: Text Constant, Numeric Constant, Date Constant, Build Date (assembles a date from year/month/day components, such as the first day of a hire month or last day of a fiscal year), and Prompt for Value (exposes a runtime prompt to the person running a report instead of hardcoding a constant inside a filter or condition).
What changes on Prism Analytics data sources
If you build custom reports on a Prism Data Source, Workday restricts calculated fields because a Prism data source has an isolated primary business object and stores only the unique identifier (WID)—not the display name—on Instance and Multi-Instance fields.
On Prism data sources, Workday supports only 17 calculated field functions: Arithmetic Calculation, Build Date, Concatenate Text, Convert Text To Number, Date Constant, Date Difference, Evaluate Expression, Format Date, Format Number, Format Text, Increment or Decrement Date, Lookup Date Rollup, Numeric Constant, Substring Text, Text Constant, Text Length, and True/False Condition. Furthermore, you cannot pass Prism Instance or Multi-Instance fields into Format Text or Substring Text because those fields carry only the WID rather than display text.
Building and verifying calculated fields in kiweely
Instead of guessing which business object holds a field or clicking through four nested creation screens by hand, you can ask kiweely in plain English to build or trace a calculated field in your connected tenant. The agent inspects your tenant's live business objects and existing field definitions, constructs the full TF → ESI → LRV or Evaluate Expression chain with your approval, and tests the result against real worker or transaction instances so you can verify the output before attaching it to a report or business process.