Skip to content
KiweelyKiweelyKiweely

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.

  • Checked against Workday on
  • Applies to Workday Query Language
  • 4 min read
  • Published
  • By Kiweely
On this page

Why WQL Throws HTTP 400 Parms are required for the fields or data source in the query

When executing a WQL query against GET /wql/v1/data or POST /wql/v1/data, Workday returns HTTP 400 Bad Request with the message:

text
Parms are required for the fields or data source in the query. Provide a value for the prompt.

This error frequently appears on queries that previously worked in a tenant or that select multiple calculated fields (cf_...) from compensation, financial, or HCM data sources such as allCompensationReviewProcessEmployeeAdjustments:

sql
SELECT
  cf_ZCF_AC_MeritForStructureInEUR,
  cf_CF_AC_Q2_Q1,
  cf_check AS Quartile,
  cf_CF_LVAOD_AnnualSalaryFeb28,
  cf_CF_LVAOD_CompensationGradeProfile AS CompensationGradeProfile,
  sharedParticipationCompensationReview,
  cf_mandatoryBudget,
  employee,
  potential AS Potential,
  employee{worker, meritPlans_PlanDetails, employeeID, company, compensationGrade, managementLevel, salaryPlanAssignmentDetails} AS Employee,
  currentPerformanceRating,
  cf_ZCF_LRV_CalibrationValue,
  cf_ZCF_AC_MeritInEURForPerformance,
  cf_ZCF_AC_ProposedAnnualSalary,
  cf_ZCF_EE_PerformanceFactor,
  cf_ZCF_AC_BaseIncreasePct,
  cf_ZCF_AC_BaseIncreaseAmount
FROM allCompensationReviewProcessEmployeeAdjustments
WHERE employee.company IN ('7b24988d32d81000fc7600a9a08f0000')
  AND compensationGrade IN ('819a9c0037531000b9a8591b82be0000')
  AND sharedParticipationCompensationReview IN ('c3f3a8044bc61000b496d388b54c0000')
  AND employee IS NOT EMPTY

In WQL, required parameters come from three places:

  1. The data source itself, which may require built-in prompts (such as company on contractRateSheetsForCompany or startDate/endDate on bonusAndOne_TimePayments).
  2. A data source filter specified in FROM dataSource(dataSourceFilter = filterAlias, ...), which defines its own required filter prompts.
  3. A report field or calculated field in the SELECT, WHERE, or WHERE ON clause that depends on a runtime prompt.

When a query suddenly starts failing with Parms are required for the fields or data source in the query even though the WQL string itself did not change, a report administrator or developer has usually modified one of the referenced calculated fields (cf_...)—or a nested sub-calculation inside its hierarchy—to use a Prompt for Value function, a Lookup Value as of Date (LVAOD) referencing a date prompt, or a Convert Currency calculation that prompts for an exchange rate date or target currency.

Isolating Which Field or Data Source Requires a Prompt

When a query selects a dozen cf_ fields, Workday’s HTTP 400 error message does not name the specific field whose prompt is missing. Use a binary elimination check in the tenant to pinpoint the culprit:

  1. Run a minimal baseline query in View WQL Query Result with a single delivered field and LIMIT 1 to verify whether the data source itself requires a parameter:
    sql
    SELECT employee
    FROM allCompensationReviewProcessEmployeeAdjustments
    LIMIT 1
  2. If the baseline query fails with the same prompt error, inspect the data source metadata via GET /wql/v1/dataSources/{ID} (and GET /wql/v1/dataSources/{ID}/dataSourceFilters/{subresourceID} if using a filter) to list its required parameter aliases.
  3. If the baseline query succeeds, add the WHERE conditions back, then re-introduce the cf_... fields in halves until the error reappears. Pay particular attention to Lookup Value as of Date (cf_CF_LVAOD_...), Arithmetic Calculation (cf_ZCF_AC_...), and Lookup Related Value (cf_ZCF_LRV_...) fields that reference currency conversions or effective dates.

You can also inspect field-level parameter requirements programmatically by calling GET /wql/v1/dataSources/{ID}/fields?field={fieldAlias} or by building a temporary custom report with those fields and running the Convert Report to WQL task. When you run Convert Report to WQL, Workday prompts you for every required field and data source parameter on the launch screen and outputs the exact PARAMETERS clause at the top of the generated WQL statement.

Fixing the Query: PARAMETERS Clause vs. Non-Prompted Calculated Fields

Once you identify the missing prompt parameter, you have two ways to resolve the HTTP 400 error depending on whether the parameter belongs to a delivered field/data source or a custom calculated field.

Option 1: Supply the Prompt Value in the PARAMETERS or FROM Clause

WQL provides two places to pass prompt values, governed by strict placement rules:

  • Report field parameters must be specified in the PARAMETERS clause at the very beginning of the WQL query (before SELECT). They cannot be placed inside the FROM clause parentheses.
  • Data source and data source filter parameters can be specified either in the PARAMETERS clause or inside the FROM dataSource(...) parentheses, but not in both.
  • The dataSourceFilter assignment itself must always remain inside the FROM clause.
  • Each parameter alias can only appear once in the PARAMETERS clause (PARAMETERS field1 = val1, field1 = val2 is invalid).

For example, when querying contractRates (a field that requires a reportingDate prompt) from contractRateSheetsForCompany (a data source that requires a company prompt):

sql
PARAMETERS reportingDate = '2026-01-01', company = cb550da820584750aae8f807882fa79a
SELECT contractRateSheet, contractRates
FROM contractRateSheetsForCompany

Or when combining a PARAMETERS clause with a dataSourceFilter in FROM:

sql
PARAMETERS endingCaseCreationDate = '2026-01-06 00:00:00', startingCaseCreationDate = '2025-06-06 00:00:00'
SELECT workdayID, case
FROM allCases (dataSourceFilter = casesOpenedWithinDateRangeFilter)

Option 2: Replace Prompted Calculated Fields with Context-Driven Calculated Fields

If a custom calculated field (cf_...) is triggering the prompt requirement because it was built for an interactive Custom Report with Prompt for Date 1 or a prompted currency code, avoid using that prompted calculated field in automated WQL endpoints if the prompt alias is opaque or shared across unrelated fields.

Instead, clone or update the calculated field using Create Calculated Field / Edit Calculated Field so that its effective date or currency resolves from a deterministic system or record value—such as Today, Current Moment, Pay Period End Date, or the target business object’s own currency field—rather than a runtime report prompt.

Also verify while editing your WQL string that copying queries from rich-text editors has not introduced typographic curly quotes (‘...’) around Workday IDs in IN (...) clauses; always use standard straight quotes ('...') or unquoted 32-character hex Workday IDs.

How to Verify in the Tenant

  1. Run View WQL Query Result in the tenant and execute SELECT workdayID FROM <dataSourceAlias> LIMIT 1 to confirm the data source runs without prompts.
  2. Add your calculated fields back into the SELECT list and test. If Parms are required for the fields or data source in the query appears, open the suspect calculated field via Edit Calculated Field and inspect its Prompts tab and any nested sub-calculations for runtime prompts.
  3. Either add the required PARAMETERS <promptAlias> = <value> header before SELECT (using the exact alias generated by Convert Report to WQL) or swap in a non-prompted calculated field, then confirm the query returns HTTP 200 in View WQL Query Result and your PMD or Orchestrate endpoint.

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.