Skip to content
KiweelyKiweelyKiweely

Workday calculated field not showing in a report: why it is missing from the field picker

A calculated field is missing from a report’s field picker for one of seven reasons: wrong business object, a report-specific field, report type, Optimized for Performance, field security, Authorized Usage, or a hidden curated list.

  • Checked against Workday on
  • Applies to Workday custom reports
  • 8 min read
  • Published
  • By Kiweely
On this page

A calculated field is missing from a report’s field picker when that report’s data source does not expose the business object the field was built on, or when a report setting hides it. The seven causes below cover almost every case. They are listed in the order that is quickest to rule out.

Kiweely Vine is a desktop AI agent for Workday consultants and developers (Mac and Windows) that does the Workday work in the tenant you connect: it builds calculated fields and reports in the tenant and checks that the field shows in the report. See how it works below.

The case that prompted this guide: a calculated field on the Job Requisition business object appears in some reports but cannot be selected in another. The worked example further down reproduces the closest real case, a field that lives on a different object than the report reads.

Which business object is the calculated field built on?

When you create a calculated field, the Business Object you pick decides where the field can be used and which fields it can read (Create Calculated Fields, doc.workday.com). Every report data source has a primary business object (PBO), and the picker offers that object’s fields, plus those of related business objects (RBOs) only where the report type allows it.

So the first check is a comparison of two names:

  1. Open the calculated field (View Calculated Field) and read its Business Object.
  2. Open the report definition and read the PBO of its data source.

If they are the same, go to the next section. If they differ, the field is on another object and is reachable only through a relationship. A parent and child object also differ: a child object inherits the parent’s fields and adds its own, so a field built on the child, such as Employee, is not on the parent, Worker (Workday Reporting Relationships, doc.workday.com).

Several data sources can share one primary business object. In a Dev tenant, three Job Requisition sources (All Job Requisitions, Job Requisitions by Role and Job Requisitions - Indexed) all report Job Requisition as the PBO. A field built on Job Requisition is a candidate for all three. Their field lists are the same set of 410 fields on that tenant, 13 of them calculated.

Is it a report-specific calculated field?

A report-specific calculated field is used within a single report definition (Concept: Report-Specific Calculated Fields). If the field “works in other reports”, check whether it is tenant-wide. A report-specific field made inside report A does not appear in report B. The same page says report-specific fields are unavailable for simple reports.

To use it everywhere, run the Convert Calculated Field for Report task, which turns a report-specific field into a tenant-wide one. Workday does not convert other report-specific fields that reference it, so run the Calculated Field Exception Audit or Report Specific Calculated Field Exception Audit report afterwards. You need the Custom Field Management domain for tenant-wide fields; report-specific ones use Private Calculated Field Management.

Report types differ in how far they reach from the PBO (Reference: Report Types):

Report type Fields it shows
Report typeSimple Fields it showsThe primary business object only
Report typeAdvanced Fields it showsThe primary business object and related business objects
Report typeMatrix Fields it showsLimited to the primary business object (Lookup Related Value page)
Report typenBox, Search Fields it showsIndexed data sources only (Indexed Data Sources page)

A calculated field on a related object appears in an advanced report only after you add that object in the Business Object column. In a matrix report it never appears from a related object. Promote the value onto the PBO with a Lookup Related Value (LRV) calculated field instead. The LRV needs a one-to-one relationship between the two objects. For a chain of objects that are not directly linked, Workday’s FAQ describes a chain of LRV fields, one per hop.

Is Optimized for Performance hiding it?

On a report built on an indexed data source, the Optimized for Performance check box on the Advanced tab limits field prompts to indexed fields. Workday’s instruction is to clear the check box if you must use nonindexed fields (Create Custom Reports; Set Up Advanced Options for Custom Reports).

This matters for a Job Requisition report: Job Requisitions - Indexed is an indexed data source, and a calculated field is only offered under Optimized for Performance if Workday has indexed it. Indexing covers only fields Workday has indexed, so a calculated field nobody added to an extended indexed data source is not offered there.

You have two ways out. Clear the check box and accept slower runs on large volumes. Or have the data administrator add the field to an extended indexed data source: it takes up to 20 added fields, an hourly background job indexes them, and for each calculated field Workday creates a duplicate with the same name. Pick the duplicate in custom reports so the report still runs in Optimized for Performance mode (Concept: Extended Indexed Data Sources). Two fields with one name in the picker is therefore expected there.

Do you have access to the field’s domain?

Workday secures fields by security domain, and you need access to the domain both to use a field in a report definition and to see its data (Concept: Business Objects, Data Sources, and Fields). For calculated fields the rule extends: you can use one only if you have access to every field in its calculation (Concept: Calculated Fields Security). A field built on a custom object adds the custom object’s domain to that list.

The same page gives the run-time effect. Without authorization, a currency or numeric calculated field shows zero and every other type shows blank. If the field is in the picker but shows blank or zero for one person, see why a calculated field returns blank.

Is Authorized Usage restricting it?

The Create Calculated Field task has an optional Authorized Usage prompt, which enables where the field can be used. Workday also notes that a field is usable in any area when its Authorized Usage is Default Areas, and that you can check it from the field’s related actions menu. A field limited to a specific area, such as Calculation Engine (Payroll/Absence), does not show up elsewhere.

Is a curated field list switched on?

Administrators can configure a curated field list for a business object so users find fields faster in Matrix and Advanced reports. All data sources with that primary business object share the list. When the report’s related actions menu has Show only curated fields set to On, the picker shows only the configured fields; Off shows all available fields (Set Up Curated Field Lists for Reporting). A new calculated field is absent until someone adds it with the Maintain Field Lists for Reporting report.

Worked example: a Worker field on a Job Requisition report

Setup in the Dev tenant, using read-only WQL metadata calls on 16 November 2026:

  1. GET .../dataSources?alias=allJobRequisitions returned the data source with primary business object Job Requisition.
  2. GET .../dataSources/{id}/fields listed 410 fields on it. Thirteen had the cf_ alias prefix Workday gives calculated fields, for example cf_jobTitleFromJobProfile (Text).
  3. The same call on All Workers listed 183 cf_ fields, a different set. None of the 183 appeared in the Job Requisition list.

So a calculated field built on Worker, such as cf_workerStatus, is not a Job Requisition field. Selecting it straight from the requisition source fails:

SELECT jobRequisition, cf_workerStatus FROM allJobRequisitions LIMIT 2
Enter a valid report field. This field is invalid: cf_workerStatus.

The field is reachable through a relationship. In WQL, related fields go in curly brackets after the instance field that links to them (Related Business Objects in WQL):

SELECT jobRequisition, primaryRecruiter{cf_workerStatus} FROM allJobRequisitions LIMIT 2

This returned Active for the primary recruiter on both rows (R-00007 Call Center Manager and R-00008 Senior Call Center Operator, Workday demo data).

The report writer has the same two routes:

  • In an advanced report, add Primary Recruiter in the Business Object column, then choose the Worker calculated field in the Field column.
  • For a matrix report, or to filter and group, create an LRV on Job Requisition: Lookup Field Primary Recruiter (a single-instance field), Return Value the Worker calculated field. The new field belongs to Job Requisition, so it appears in every Job Requisition report.

Primary Recruiter is single instance. Hiring Manager, Recruiter and Worker are multi-instance on the same source, so an LRV cannot read them directly. First use an Extract Single Instance field to pick one (see Extract Single Instance).

How can WQL help you check?

WQL lists every field a data source exposes, with its alias and type, and shows which fields are calculated. It is the quickest way to see whether a field belongs to a source at all. It does not apply the report writer’s Optimized for Performance filter, curated lists or your security, so a field present in WQL can still be hidden in the picker for the reasons above. Use it to settle the business-object question first.

Kiweely Vine is a desktop AI agent for Workday that answers Workday questions and can read a client’s tenant with consent, so a check like this can run against the tenant instead of by hand.

Where Kiweely fits

Kiweely Vine is a desktop AI agent for Workday consultants and developers (Mac and Windows) that does the Workday work in the tenant you connect. It builds calculated fields and the reports that use them in your tenant.

In a recorded run in Kiweely’s own Workday Development tenant (with fictional sample data, not a customer result), Vine designed and built a complex calculated field (benefits review status, from employment status, worker type, FTE, service dates and a 90-day wait) and used it in a saved report in 50 minutes. An independent acceptance passed all 6 checks it ran; boundary cases were checked in the saved rules, not executed (watch the film).

Vine Free is $0 on a personal developer tenant with $5 of Kiweely Credits included, and Vine Personal ($99/month) and Vine Team ($149/seat/month) connect to any Workday tenant (pricing). Start free.

Frequently asked questions

Why can I use a calculated field in one Workday report but not another?

Because each report offers the fields of its own data source's primary business object, plus related objects in an advanced report. A field built on a different business object, or a report-specific field owned by another report, is not in the list.

What does Optimized for Performance do to the field picker?

On a report built on an indexed data source it shows only indexed fields in field prompts. A calculated field Workday has not indexed is hidden until you clear the check box on the report's Advanced tab.

Can I use a calculated field from a related object without rebuilding it?

In an advanced report, yes: add the related business object in the Business Object column, then pick the field. To use it in a matrix report, or to filter or group on it, promote it with a Lookup Related Value field.

Does a missing field mean I lack security access?

It can. Workday secures fields by domain, and you need access to the domain to use a field in a report definition. A calculated field also needs access to every field it reads.

Can WQL tell me whether a calculated field belongs to a data source?

Yes. The data source's fields endpoint lists calculated fields with a cf_ alias, so you can see which business object's fields a source exposes. It does not reproduce the report writer's Optimized for Performance filter.

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.