You name the data source, the fields, and the filters, and Workday returns the rows. Custom reports exposed as web services (RaaS) are a separate route.
What it means in practice
- It looks like SQL, but the names come from Workday: data sources, fields, filters, and aliases are Workday’s vocabulary, and they differ from tenant to tenant.
- WQL follows the asker’s Workday security. The same query can return different rows for different people, because it only sees what each person is allowed to see.
- It is not full SQL: there is no SELECT *, no LIKE, and results come back in pages: large answers need pagination, not one giant pull.
- The reliable way to write WQL is to start from the tenant’s own metadata: find the data source first, then its fields and the prompts its filter requires.
With Kiweely Vine
Kiweely Vine writes WQL against your connected tenant’s actual metadata (the data sources, fields, and aliases Workday exposes to you) instead of guessing names from another tenant or an old example. It runs the query, shows you what came back, and Workday’s own validation says whether it passed.