A calculated field shows up in a report’s field picker only when Workday associates it with the business object you are reporting on. Create it on that object (tenant-wide) or as a report-specific calculated field on this report. Fields built for another object or locked inside another report’s definition will not appear.
Business object owns visibility
Workday Education’s calculated-fields topic states that every calculated field is associated with a business object. That object decides which fields you can use inside the calculation and where the finished field appears in prompts and reports. A field built on Worker behaves like other Worker fields; it will not show as a peer field on an unrelated primary business object.
Before you rebuild anything, locate existing fields with:
- Maintain Calculated Fields (system-wide calculated fields)
- All Calculated Fields (optionally filtered to one business object)
- Business Object Details (delivered and calculated fields on an object)
- Report Fields (field references across the tenant)
Report-specific vs tenant-wide
From Concept: Report-Specific Calculated Fields:
| Kind | Where it lives | Picker behavior |
|---|---|---|
| KindReport-specific | Where it livesSingle report definition | Picker behaviorAvailable in that report’s prompts (Columns, Filter, Matrix, and so on as documented)—not as a general tenant field |
| KindTenant-wide | Where it livesTenant calculated-field library on a business object | Picker behaviorAvailable wherever that business object’s fields are used |
Create report-specific fields from the custom report’s related actions (Calculated Field for Report → Create Calculated Field) or from Create Calculated Field for Report on the report’s Business Object / Columns (and other listed tabs). On advanced reports, the Columns-tab create prompt is for report owners only.
Workday states report-specific calculated fields are unavailable for simple reports.
To reuse a report-specific field elsewhere, run Convert Calculated Field for Report to make it tenant-wide. Workday does not automatically convert other report-specific fields that reference the converted one—use Calculated Field Exception Audit / Report Specific Calculated Field Exception Audit for errors, and Calculated Field Usage Hierarchy before risky edits.
Security that hides create (and therefore “missing” fields)
Changing calculated fields can affect financial reports, hiring processes, and auditor reports. Workday points administrators at the Private Calculated Field Management domain to control who can create, change, or delete report-specific calculated fields. If you can only create report-specific fields, you will not see a path to a tenant-wide field on the object you expect—another reason a “shared” field never appears in a second report’s picker.
Checklist when the picker is empty
- Confirm the report’s primary (or selected) business object matches the calculated field’s object.
- Search All Calculated Fields / Business Object Details for the name on that object.
- If it was built under another report, open that report or convert it to tenant-wide.
- If you are on a simple report, switch to an advanced (or other supported) report type before using report-specific calculated fields.
- Confirm your security allows viewing or creating the field type you expect.
Blank values after the field appears are a different problem—see calculated field returns blank.