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:
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 aCaseorWorkerbusiness 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 Dateor an action event onResolve 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 theTerminationorResolve Casebusiness 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:
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:
- Open App Manager in the tenant (or configure ISU Authentication for the app).
- Register the Integration System User and link the API Client for Integrations (which must include the
Systemfunctional area scope for WQL). - If the app was promoted to a non-development tenant (
IMPL,SBX, orPROD), 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
- To diagnose
"Specify a valid report field", decompose the Calculated Field: list every intermediate and leaf field referenced bycf_...directly inSELECT fieldA, fieldB, fieldC FROM <dataSource> LIMIT 1and run View WQL Query Result while proxied as the ISU. Whichever underlying field fails identifies the exact domain or Business Process Security Policy missingViewaccess on the ISSG. - 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.
- Sign in as the ISU, run the query in REST API Explorer to confirm a
200 OKJSON response, and then load the Extend PMD page to verify theisuAuthendpoint succeeds.