A WQL query that came from Convert Report to WQL breaks after a field rename because the saved query still names the old alias. Workday embeds report heading overrides and calculated-field aliases into the query text. Renaming the field in Report Writer does not rewrite every integration that already stored that string.
How aliases get into the converted query
Workday’s Convert Report to WQL documentation is explicit:
- Values in Column Heading Override become aliases in the converted WQL.
- For fields from related business objects, values in Group Column Heading become the aliases.
The WQL SELECT reference says you select fields by WQL alias. If two fields share an alias, WQL returns the first one defined. Custom aliases in AS clauses are optional renames in the response, not substitutes for a missing field alias.
Calculated-field aliases are editable. Workday creates them, and you can change them. A rename there has the same effect as changing a heading override: every saved query that still uses the previous token fails with an invalid field message.
What you see after a rename
Typical outcomes after someone edits the report or the calculated field:
| What changed | What breaks |
|---|---|
| What changedColumn Heading Override text | What breaksConverted AS alias and any hand-copied override no longer match the report |
| What changedGroup Column Heading for an RBO block | What breaksRelated-object group alias in the converted query is stale |
| What changedCalculated field WQL alias | What breaksSELECT / WHERE tokens that used the old cf_… (or edited) alias fail |
| What changedField removed from the report | What breaksConvert Report to WQL no longer emits it; old queries still ask for it |
Workday does not publish a dedicated “field was renamed” error string for this case. The failure you get is the ordinary invalid-field path: the alias in the query is not one Workday exposes on that data source for the calling user. The WQL error guide covers the exact wording Workday returns for an invalid report field.
Fix the query, not only the report
- Open the report and note the current Column Heading Override, Group Column Heading, and each calculated field’s WQL alias.
- Run Convert Report to WQL again on the current report definition. Prefer the new string over hand-editing a long query unless you know every token.
- Replace the query in every integration, orchestration, or notebook that still holds the previous conversion.
- Confirm aliases with
GET /dataSources/{ID}/fieldsor the field’s related actions before you mark the change done. - If conversion lists components it cannot convert, fix those separately. A rename can surface a calculated field that also lacks an adhoc alias.
Keep renames from breaking consumers
Treat heading overrides and calculated-field aliases as API contracts once anything outside Report Writer depends on the converted query. Before you rename:
- Search for the current alias in Studio, Orchestrate, and any stored WQL.
- Change the alias or override once.
- Re-convert and update every consumer in the same change.
- Run the smallest
SELECTthat names the renamed field against the same account the integration uses.
Audience Builder’s invalid-report-field troubleshooting also notes that the user who converts to WQL and the user who runs the query must both have access to the field. After a rename, confirm security as well as spelling.
Kiweely Vine can compare a stored WQL string to the current field list on a connected tenant when you ask it to. You still decide the alias names in Workday.
Frequently asked questions
I renamed a report column. Why does my old WQL fail?
The saved query still uses the previous alias. Convert Report to WQL embeds Column Heading Override and Group Column Heading values as aliases. After a rename, re-convert or update the SELECT list.
Does changing a calculated field alias break Convert Report to WQL?
Yes for any query that still selects the old alias. Workday lets you edit calculated-field aliases; every consumer must use the new one.
How do I pick the correct alias after a rename?
Call GET /dataSources/{ID}/fields or view the field’s WQL alias from related actions, then replace the token in the query.