---
title: "Why does Convert Report to WQL say this field is missing…"
description: "Convert Report to WQL stops when a calculated field has no WQL alias. Give the field an alias, or drop it from the report and re-convert."
url: https://kiweely.com/guides/convert-report-to-wql-adhoc-alias
---

# 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 November 17
-   Applies to **Workday WQL and Convert Report to WQL**
-   3 min read
-   Published November 17
-   By Kiweely

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 |
| --- | --- |
| Related actions on the field, calculated field, or data source | The WQL alias shown in the tenant |
| Custom report on the **WQL Alias** report field | Aliases for data sources enabled for reporting |
| `GET /dataSources/{ID}/fields` | Field 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

-   [Convert Reports to WQL Queries](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/workday-query-language-wql-/zyr1612554181816.html)
-   [Reference: WQL Aliases](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/workday-query-language-wql-/ktw1644956621314.html)
-   [Concept: Workday Query Language (WQL)](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/workday-query-language-wql-/aht1611188422513.html)

## Related guides

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

-   [### Why does Convert Report to WQL break after a field rename? Convert Report to WQL embeds heading overrides and calculated-field aliases in the query. After a rename, re-convert the report or update every saved WQL string to the aliases Workday exposes now.](https://kiweely.com/guides/workday-convert-report-to-wql-after-field-rename)
-   [### Should I use RaaS, WQL or the REST API to extract data from Workday? Use RaaS for a saved report’s output, WQL for a filtered, grouped or paged extract of up to 1 million rows, and REST for small, low-latency reads of one resource. Limits and sources are in the table.](https://kiweely.com/guides/workday-raas-wql-rest)
-   [### 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)

-   [How do I build a Workday integration inventory report with every integration system, its template, schedule, last run and owner?](https://kiweely.com/guides/workday-integration-inventory-report-wql)
-   [Retrieving Eligible Absence Plans and Live Balances for a Worker via Workday APIs](https://kiweely.com/guides/workday-absence-balances-api-eligible-plans-for-worker)
-   [Querying the Workday Worker Directory, Supervisory Hierarchy, and Cost Centers with WQL](https://kiweely.com/guides/workday-worker-directory-org-chart-search-fields-wql)
-   [Querying Open Job Requisitions and Supervisory Org Headcount via Workday Staffing APIs](https://kiweely.com/guides/workday-staffing-api-job-requisitions-open-positions-managers)
-   [Finding Unsubmitted Workday Time Blocks and Project Hours with WQL](https://kiweely.com/guides/workday-project-time-tracking-unsubmitted-hours-wql)
-   [Querying Pending Workday My Tasks and Inbox Approvals via API and WQL](https://kiweely.com/guides/workday-inbox-my-tasks-awaiting-action-rest-wql)
-   [Why fileLength on workerDocuments Returns 52 in WQL for Business Process Attachments](https://kiweely.com/guides/wql-workerdocuments-filelength-returns-52)
-   [Paging with POST /wql/v1/data in a PMD Grid When Queries Exceed URL Limits](https://kiweely.com/guides/wql-post-data-endpoint-grid-pagination-url-limit)

### From the blog on WQL

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

-   [Answering Executive Span-of-Control and Headcount Questions Live from Workday](https://kiweely.com/blog/executive-org-span-of-control-attrition-questions-live-workday)
-   [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)

## 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.
