---
title: "Fixing WQL Calculated Field & HTTP 500 Errors for an ISU"
description: "Resolve \"Specify a valid report field. This field isn't valid in WQL\" and HTTP 500 errors when an Integration System User (ISU) runs WQL queries with…"
url: https://kiweely.com/guides/wql-calculated-field-isu-specify-valid-report-field-500
---

# Fixing WQL “Specify a valid report field” and HTTP 500 Errors When an ISU Queries Calculated Fields

A WQL query with calculated fields that succeeds for an SSO user can fail for an Integration System User (ISU) with “Specify a valid report field. This field isn’t valid in WQL” or HTTP 500. Learn how WQL View permissions, nested CF security, and App Manager ISU registration work.

-   **Checked** against Workday on November 6
-   Applies to **Workday Query Language**
-   4 min read
-   Published November 6
-   By Kiweely

## Why WQL Rejects a Calculated Field for an ISU with `Specify a valid report field`

When you test a WQL query containing a Calculated Field (`cf_...`) in **View WQL Query Result** as an administrator or standard user, it runs cleanly. Yet when you proxy as an Integration System User (ISU)—or invoke the query from an Extend endpoint configured with `"authType": "isuAuth"`—Workday rejects the query with:

text

```
Specify a valid report field. This field isn't valid in WQL.
```

WQL does not distinguish between a non-existent field alias and a field that the executing user lacks security permission to read; in both cases, Workday hides the field from the user’s schema and returns `Specify a valid report field. This field isn't valid in WQL.`

### Root Cause 1: Missing Domain `View` or Business Process `View All` on Nested Source Fields

A Calculated Field in Workday does not have its own standalone domain security policy. Instead, Workday evaluates security on **every underlying source field, related business object link, and intermediate calculated field** inside the calculation hierarchy:

-   If a `Lookup Related Value` (`cf_...`) looks up a field from a `Case` or `Worker` business object, the ISU’s Integration System Security Group (ISSG) must have permission to the domain securing both the lookup relationship field and the target field.
-   If a calculated field references a Business Process event field—such as a worker’s `Termination Date` or an action event on `Resolve Case`—domain permissions alone are not enough. The ISSG must also be granted **View All** (or the appropriate view permission) on the corresponding **Business Process Security Policy** (such as the `Termination` or `Resolve Case` business process policy).
-   Check that the Calculated Field itself is marked **Authorized for Use** (shared with all users or with the ISSG) under **Edit Calculated Field**.

### Root Cause 2: `View` Permissions vs. Integration `Get` Permissions in WQL

A frequent question when configuring an ISSG for WQL is whether the security group needs **Report/Domain `View`** permission or **Integration `Get`** permission on the underlying domains.

Because WQL is built on Workday’s reporting engine rather than SOAP web services, **WQL primarily evaluates Report Field / Domain `View` permissions** (along with the `Workday Query Language` and `WQL for Workday Extend` domains in the `System` functional area), plus **View All** on any referenced Business Process Security Policies. While certain domains expose report fields to `Get` permissions as well, relying on `Get` alone will leave report-only fields and calculated fields invisible to the ISU. Always grant **View** access on the domain security policies for all data sources, data source filters, and fields used in WQL, and run **Activate Pending Security Policy Changes** after updating any policy.

## Why a PMD Inbound Endpoint with `authType: "isuAuth"` Returns HTTP 500

Even more puzzling is when you sign in to the tenant directly as the ISU, run **View WQL Query Result** with your exact query, and see valid rows—yet calling the same query from an Extend PMD inbound endpoint configured with `"authType": "isuAuth"` fails with HTTP `500 Internal Server Error`:

sql

```
PARAMETERS endingCaseCreationDate = '2026-01-06 00:00:00'
SELECT workdayID, case, cf_CFX_LRV_CaseTypeWID
FROM allCases (
  dataSourceFilter = casesOpenedWithinDateRangeFilter,
  startingCaseCreationDate = '2025-06-06 00:00:00'
)
WHERE (
  casePurged = false
  AND caseCreationDate >= '2025-06-06 00:00:00'
  AND caseCreationDate <= '2026-01-06 00:00:00'
)
```

When a WQL query works in **View WQL Query Result** as the ISU but returns HTTP `500` in an Extend PMD endpoint using `isuAuth`, check three specific configuration points:

### 1\. Simplified ISU Registration in App Manager

Creating an ISU and an API Client in the tenant is not enough for an Extend app’s `isuAuth` endpoint to impersonate that ISU. You must register the Simplified ISU to the specific Extend application in **App Manager**:

1.  Open **App Manager** in the tenant (or configure ISU Authentication for the app).
2.  Register the Integration System User and link the API Client for Integrations (which must include the `System` functional area scope for WQL).
3.  If the app was promoted to a non-development tenant (`IMPL`, `SBX`, or `PROD`), run **Modify Authorized Non-Development Tenants for API Clients using ISU Authentication** so the gateway permits token exchange for that tenant.

### 2\. Escaping Quotes Around DateTime Parameters in PMD JSON

Notice that DateTime literals (`'2025-06-06 00:00:00'`) contain a space between the date and time. In **View WQL Query Result**, single quotes work directly. When embedded inside a PMD `.pmd` or `.wqlquery` JSON string, unescaped quotes or typographic smart quotes (`‘2025-06-06 00:00:00’`) break the WQL request parser or URL encoding and trigger an HTTP `500` from the WQL gateway. Use standard ASCII single quotes `'2025-06-06 00:00:00'` or escaped double quotes `\"2025-06-06 00:00:00\"` inside the PMD `wqlQuery` block.

### 3\. Testing in REST API Explorer as the ISU

Note that you cannot test a Workday Cloud Platform API Gateway URL (`https://api.workday.com/wql/v1/data`) in Postman using HTTP Basic Authentication (`Username/Password`)—WCP gateway endpoints strictly require an OAuth 2.0 Bearer access token. To isolate whether an HTTP `500` is caused by the WQL string or the Extend app’s `isuAuth` binding, sign in to the tenant directly as the ISU and execute the request inside **REST API Explorer** (`GET /wql/v1/data`).

## How to Verify in the Tenant

1.  To diagnose `"Specify a valid report field"`, decompose the Calculated Field: list every intermediate and leaf field referenced by `cf_...` directly in `SELECT fieldA, fieldB, fieldC FROM <dataSource> LIMIT 1` and run **View WQL Query Result** while proxied as the ISU. Whichever underlying field fails identifies the exact domain or Business Process Security Policy missing `View` access on the ISSG.
2.  Run **View Security for Securable Item** on that field, add the ISSG with **View** permission (and **View All** on any required BP policy), and run **Activate Pending Security Policy Changes**.
3.  Sign in as the ISU, run the query in **REST API Explorer** to confirm a `200 OK` JSON response, and then load the Extend PMD page to verify the `isuAuth` endpoint succeeds.

## Sources checked

-   [Concept: Workday Query Language (WQL)](https://developer.workday.com/documentation/GUID-6546152a-bcf0-447d-8d64-230f9e2ac291-enHYPHENus)
-   [Concept: ISU Authentication](https://developer.workday.com/documentation/GUID-cb3e0fcd-bb97-4005-8d10-3a02e88dab71-enHYPHENus)
-   [Steps: Set Up ISU Authentication for Apps](https://developer.workday.com/documentation/GUID-3277fec3-24c9-41da-9840-c61b41033f28-enHYPHENus)
-   [Concept: Report Security](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/workday-reporting-concepts/dan1370797778178.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Fixing WQL Error “Empty Required Parm Moment\_Parm” with SUM() Combining SUM() and GROUP BY on currency fields in compensation data sources like bonusAndOne\_TimePayments can trigger S24 “Empty Required Parm Moment\_Parm (21$9232)”. Learn how currency moment evaluation works in WQL and how to structure or fall back when aggregating payment amounts.](https://kiweely.com/guides/wql-empty-required-parm-moment-parm-sum)
-   [### Fixing WQL HTTP 400 “Parms are required for the fields or data source in the query” A WQL query returns HTTP 400 “Parms are required for the fields or data source in the query. Provide a value for the prompt” when a data source filter or calculated field requires a runtime prompt parameter. Learn how to isolate prompted cf\_ fields and pass values via PARAMETERS or FROM.](https://kiweely.com/guides/wql-400-parms-are-required-for-fields-or-data-source)
-   [### What is Workday Query Language (WQL), and how do you write and run a query? Workday Query Language (WQL) is Workday’s SQL-like language for reading data from data sources and fields instead of reports. You need the Workday Query Language domain in the System functional area; an external caller also needs an API client with System scope.](https://kiweely.com/guides/workday-wql)
-   [### Why does my Workday WQL query fail? The exact error messages and how to fix each one Workday has no WQL message worded ‘instance set invalid for prompt’. A rejected prompt value returns ‘Invalid Parameter Values for parameter’ or ‘does not meet the restrictions defined for this field’. This page quotes each common error as Workday returned it, with the fix.](https://kiweely.com/guides/wql-error-messages)

### More guides on WQL

[All 31 guides](https://kiweely.com/guides#wql)

-   [Why WQL AVG() Rounds to Whole Numbers and How to Handle Conditional Logic Without CASE](https://kiweely.com/guides/wql-avg-integer-rounding-conditional-logic-without-case)
-   [WQL 500-Instance Related Business Object Limit and Large IN (...) Filter Limits](https://kiweely.com/guides/wql-500-rbo-instances-per-row-large-in-filter-limits)
-   [Custom Agent Actions that call Workday SOAP, REST and WQL](https://kiweely.com/guides/workday-custom-agent-actions-soap-rest-wql)
-   [Running WQL in Orchestrate as an integration system user: the security it needs](https://kiweely.com/guides/workday-orchestrate-wql-as-isu)
-   [WQL Cheat Sheet: Workday Query Language Syntax, Data Sources and Working Examples](https://kiweely.com/guides/workday-wql-cheat-sheet)
-   [Workday Prism Analytics vs. WQL vs. Custom Reports: Joining External and Tenant Data](https://kiweely.com/guides/workday-prism-analytics-vs-wql)
-   [Should I use RaaS, WQL or the REST API to extract data from Workday?](https://kiweely.com/guides/workday-raas-wql-rest)
-   [How do I get more than 500 rows from a Workday WQL query?](https://kiweely.com/guides/wql-more-than-500-rows)

### From the blog on WQL

[All posts](https://kiweely.com/blog)

-   [Build vs. Buy a Workday MCP Server: OAuth 2.1, SOAP, WQL, and Twice-Yearly Releases](https://kiweely.com/blog/build-vs-buy-workday-mcp-server-engineering-cost)
-   [What happens after ChatGPT writes your WQL query](https://kiweely.com/blog/after-chatgpt-writes-your-wql)
-   [Answering Executive Span-of-Control and Headcount Questions Live from Workday](https://kiweely.com/blog/executive-org-span-of-control-attrition-questions-live-workday)

## Let Workday check the work.

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

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

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