A vendor needs to create a Date Difference calculated field. However, the two dates needed for that calculation are on two separate business objects…

The 'Date Difference' calculated field requires both date fields to exist on the same business object. When the dates are on two separate, but related, business objects, you must first bring one date into the context of the other. The Lookup Related Value (LRV) calculated field is designed for this exact purpose. It retrieves the value of a field from a related business object, making it available for use in calculations on the primary business object. Therefore, an LRV field must be created first to "pull" the remote date, which can then be used in the 'Date Difference' calculation.

B. Build Date: This field type constructs a new date from separate year, month, and day components; it does not retrieve an existing date from another business object.

C. Lookup Date Rollup: This field aggregates date values (e.g., finds the earliest or latest date) from multiple instances of a related business object, not retrieve a single specific date.

D. Lookup Value as of Date: This field retrieves the value of an effective-dated field as of a specific moment in time, which is not the primary function needed to simply traverse a business object relationship.

1. Workday Official Documentation

"Calculated Fields: Reference": This guide details the function of each calculated field type. The section on Lookup Related Value explicitly states its purpose is to "return a value from a related business object." This directly addresses the problem of accessing a field (the date) that resides on a separate business object.

2. Workday Official Documentation

"Calculated Fields: Key Concepts": This document explains that calculations can only be performed on fields available on the report's primary or related business objects. To use a field from a related object

it must be brought into the context of the calculation. The LRV is presented as the standard mechanism for this data retrieval across related objects. The documentation for the Date Difference calculated field confirms that its input parameters must be fields accessible from the business object on which the calculation is being defined.