Skip to content
KiweelyKiweelyKiweely

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.

  • Checked against Workday on
  • Applies to Workday Calculated Fields
  • 4 min read
  • Published
  • By Kiweely
On this page

Lookup Related Value (LRV) looks up a field on a related business object and returns that value on the primary business object of the calculated field, but only when the relationship is one-to-one. Promoting the field onto the primary object is what lets you filter, group, sort, summarize, and drive business process condition rules without adding a related-business-object column that fans the report into one row per related instance (and blank cells where the relationship is missing).

On an advanced report, adding a column from a related business object can expand each primary instance into multiple output rows. Workers without that related data still appear with blank related cells unless you also filter those primaries out. That pattern is fine for detail dumps. It is the wrong pattern when you need:

  • One row per worker on a headcount or compensation matrix
  • A filter or sort on manager email, retention-bonus percentage of base pay, or another related scalar
  • A business process condition rule that must evaluate fields Workday did not expose on the event object
  • Grouping and totaling on an advanced report using a field that originally lived on a related object

LRV solves those cases by copying the related value onto the primary object at runtime. Workday never stores calculated field values; the promotion resolves when the report, integration, or condition rule runs.

One-to-One Is Mandatory: Prove It Before You Build

Workday’s Administrator Guide and Reporting course both state the same rule: there must be a one-to-one relationship between the primary business object and the related business object for Lookup Related Value. Use Business Object Details to confirm whether the connecting field is single-instance (1:1) or multi-instance (1:M).

Relationship You See Correct Pattern Wrong Pattern
Relationship You SeeSingle-instance field already on the PBO (for example Worker Manager) Correct PatternLRV with that field as Lookup Field Wrong PatternN/A
Relationship You SeeMulti-instance field (for example Performance Reviews, Dependents) Correct PatternExtract Single Instance first, then LRV Wrong PatternLRV pointed directly at the multi-instance field
Relationship You SeeObjects not directly linked (for example Worker to Time Sheet via Time Block) Correct PatternChain of LRV hops through the intermediary Wrong PatternOne LRV hoping Workday will invent the path
Fails
# Anti-pattern: LRV on a multi-instance hop
Business Object: Worker
Function:        Lookup Related Value
Lookup Field:    Performance Reviews   # multi-instance / 1:M
Return Value:    Overall Rating
# Workday requires 1:1; this is the wrong function for the hop
Works
# ESI creates the 1:1 hop, then LRV promotes the scalar
CF_ESI_Latest_Review (Extract Single Instance on Performance Reviews)
CF_LRV_Latest_Rating (Lookup Related Value)
  Lookup Field:  CF_ESI_Latest_Review
  Return Value:  Overall Rating

Official use cases include promoting a manager’s email onto Worker reporting, expanding fields available inside business process condition rules, promoting related fields for matrix reports (which limit fields to the PBO), enabling grouping and totaling on advanced reports, and combining a related field with a PBO field in another calculated field.

  1. Open Create Calculated Field (secured by Custom Field Management in the System functional area).
  2. Choose the business object where you need the promoted field to appear.
  3. Select Function Lookup Related Value.
  4. On the Calculation tab, set Lookup Field to a self-referencing or single-instance field.
  5. Set Return Value to a field associated with that Lookup Field’s related business object.
  6. Optionally, on Additional Info under Advanced Options, select Use Return Value Field Formatting when you need the return field’s date precision, alternate display ID, numeric rounding, or rich text formatting retained for report run and PDF/XML export.

Indexed report data sources and indexed field conditions can speed filtering for many report types when you index the calculated field. Workday documents that indexing does not apply the same way for composite and simple reports.

Blank Rows vs Blank Cells: What LRV Changes

LRV does not invent missing related data. If the Lookup Field is blank for a primary instance, the LRV return is blank. What changes is row shape:

Design Row Behavior When to Use
DesignRelated business object column on advanced report Row BehaviorCan multiply rows; blanks appear on related cells When to UseDetail listings where multiple related rows are the point
DesignLRV on primary business object Row BehaviorKeeps one primary row; blank only in the promoted cell When to UseFilters, grouping, matrix axes, condition rules, one-row-per-worker outputs
DesignESI + LRV Row BehaviorOne primary row; blank when no related instance matches the ESI condition When to UseLatest review rating, primary dependent name, current medical plan ID

If every row looks blank after an LRV change, verify security with View Security for Securable Item, confirm the Lookup Field is populated on sample instances, and inspect the chain with Calculated Field Usage Hierarchy. See also why a calculated field returns blank and matrix report aggregations.

Business Process and Multi-Hop Patterns

Business process condition rules only see fields on objects related to that process. When the rule needs a field that lives elsewhere, promote it with LRV onto an object the process already exposes (for example Worker Business Process or Action Event), chaining hops when needed. Workday’s calculated fields FAQ uses notice-period rules and Worker to Time Sheet paths as concrete illustrations of the same idea: move the field into the object context the rule can evaluate.

After you save, run Calculated Field Exception Audit, then place the Lookup Field, the LRV result, and a control column side by side on a test custom report for workers with and without the related instance. The proof that LRV worked is simple: one primary row per worker, correct promoted values where the relationship exists, blanks only where the Lookup Field itself is empty, and filters or matrix groupings that no longer depend on a related-object column expansion.

If you need to map a multi-hop LRV path against live tenant relationships and propose the ESI bridge where cardinality is one-to-many, Kiweely Vine can inspect the connected tenant’s business objects and draft the chain for your approval. 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

Can Lookup Related Value hop a one-to-many multi-instance field directly?

No. Workday requires a one-to-one relationship between the primary business object and the related object used by Lookup Related Value. Convert the one-to-many hop with Extract Single Instance first, then point Lookup Related Value at that single-instance field.

Why do matrix reports need Lookup Related Value for related-object fields?

Matrix reports limit available fields to the primary business object. Lookup Related Value promotes a related field onto the primary object so you can use it as a dimension, measure input, or filter without adding a related business object column that matrix reports do not support the same way advanced reports do.

Does Use Return Value Field Formatting change exported Excel values?

No. Workday retains formatting for report run and PDF or XML export when you select Use Return Value Field Formatting, but it does not retain that formatting when you export to Microsoft Excel. The option also does not affect prompts.

How do I link two business objects that are not directly related?

Build a chain of Lookup Related Value fields through an intermediary object. Workday FAQ guidance uses examples such as Worker to Time Block to Time Sheet, creating one LRV per hop until the target field sits on the business object you need.

Sources checked

Related guides

All guides

Let Workday check the work.

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

Get the next guide in your inbox.

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

We’ll email you once to confirm. Unsubscribe in one click from any issue.