Skip to content
KiweelyKiweelyKiweely

Why does Convert Report to WQL say this field is missing an adhoc alias?

Convert Report to WQL fails with “This field is missing an adhoc alias” when a calculated field has no WQL alias. Set the calculated-field alias, then convert again—or drop the field and compute outside WQL.

  • Checked against Workday on
  • Applies to Workday WQL and Convert Report to WQL
  • 3 min read
  • Published
  • By Kiweely
On this page

Convert Report to WQL fails with This field is missing an adhoc alias when a calculated field on the report has no WQL alias for Workday to put in the generated query. Delivered fields already carry aliases. Calculated fields only work in WQL through the alias Workday creates and that you can edit.

What Convert Report to WQL actually does

Workday’s Convert Report to WQL report turns an advanced or matrix report you can access into a WQL string. You complete the report’s prompts, Workday shows the query and whether it is valid, and it lists report pieces that cannot convert. You then paste the query into the WQL GET /data or POST /data call.

When the report uses Column Heading Override values, Workday includes those as aliases in the converted query. For related business object fields, it uses Group Column Heading. That is separate from the calculated-field WQL alias that the “adhoc alias” message is about.

Why calculated fields need an alias

Workday’s WQL aliases reference states that aliases identify data sources, filters, fields, calculated fields, and parameters. All Workday-delivered objects have a corresponding alias. For calculated fields, Workday creates aliases and you can edit them. Without an alias, Convert Report to WQL has no token to emit for that column, so conversion stops on that field.

Fix steps

  1. Open Convert Report to WQL, select the failing report, and note which field the conversion names.
  2. Open that calculated field. Confirm it is calculated, not a delivered field whose label you mistook for an alias.
  3. Set or edit the calculated field’s WQL alias from its related actions or additional information. Treat alias assignment as part of creating any calculated field you will report or query.
  4. Save the calculated field, then re-run Convert Report to WQL.
  5. In the generated query, refer to the field by that alias, not by the report column label.
  6. If you only needed the value once, remove the calculated field from the report, convert again, and compute the value outside WQL instead.

Confirm the alias before you ship the query

Workday documents two ways to check aliases:

Method What you get
MethodRelated actions on the field, calculated field, or data source What you getThe WQL alias shown in the tenant
MethodCustom report on the WQL Alias report field What you getAliases for data sources enabled for reporting
MethodGET /dataSources/{ID}/fields What you getField and calculated-field aliases for that data source

Copy the alias from one of those places into any hand-written WQL. Capitalization counts.

What Convert Report to WQL will not fix for you

Some report configurations never produce a valid WQL query. Workday says so on the Convert Report to WQL page and lists the non-convertible components in a table. An adhoc-alias failure is one concrete case inside that broader rule: fix the alias, or drop the field, then convert again. If the report still fails for other components, treat those rows in the conversion table as separate work.

You need the Workday Query Language domain in the System functional area to use WQL at all. The conversion user also needs access to the report and to every field the query will select.

Kiweely Vine can help you read a Convert Report to WQL result and the tenant’s field aliases when you connect a developer tenant with consent. It does not replace setting the calculated-field alias in Workday.

Frequently asked questions

What does “This field is missing an adhoc alias” mean on Convert Report to WQL?

A field on the report—almost always a calculated field—has no WQL alias for the conversion to emit. Open that calculated field, set or confirm its alias, and run Convert Report to WQL again.

Do delivered fields need an adhoc alias for Convert Report to WQL?

Workday-delivered objects already have WQL aliases. The conversion failure for a missing adhoc alias points at a calculated field that never received one you can edit.

Where do I see the alias after I fix it?

Use the related actions on the calculated field to view its WQL alias, or call GET /dataSources/{ID}/fields for the data source and copy the alias from the response.

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.