What are Calculated fields?
Calculated fields are field definitions that you configure to manipulate, transform, retrieve, and derive values based on existing data.
What are the three factors that characterize calculated fields?
- Workday calculates the value of the field based on existing data such as other Workday-delivered fields, other calculated fields, or available custom fields.
- Workday determines the value of a calculated field at runtime so that the system captures real-time data for the calculation. However, keep in mind that your tenant does not store calculated field values.
- Workday associates calculated fields with a business object. The business object determines what data to use in a calculated field and where to use the calculated field. Then, the calculated field becomes a new field on the business object.
Does the Workday system store a calculated field’s value?
No Existing data within the Workday tenant is the basis for calculated fields. The system does not store a calculated field’s value. Instead, the system pulls the value from existing fields at runtime.
When do Calculated fields resolve?
All calculated fields resolve at runtime.
Calculated fields resolve at runtime because the values of the other fields that make up the calculation of the calculated field vary. When you run the report or execute the condition rule that uses the calculated field, Workday retrieves these field and object instance values.
How do you create system-wide calculated fields?
With the “Create Calculated Field” or “Maintain Calculated Fields” tasks.
Workday automatically enables these system-wide calculated fields across the system.
What are the benefits of using system-wide calculated field?
- Availability throughout Workday, not just in reports.
- Availability in multiple reports.
- Possibility of reuse in other reports and processes avoiding duplicated calculated fields.
