ODataTailor 0.1.0 is built (21 November 2026): the workbench for OData services – free, no account, no server. What’s inside → +43 664 1964199Contact →

Querying

The request as text at the top, the builder below it, the result at the bottom. What you change in the builder shows up in the request at once – and the other way round. The query only reads: it sends GET requests only.

Options
$select, $expand, $filter, $orderby, $top, $skip, $count, $search
Result
table, JSON, Fiori
Code
UI5, CAP (cds.ql), fetch, cURL, URL
Method
GET only

The builder

  1. In the Query tab, choose the Entity set.
  2. Choose the columns under Fields ($select) and the neighbours under Navigations ($expand) – several levels deep and with their own fields.
  3. Under Filter ($filter), use Add condition to set field, operator and value. The operators fit the type: comparisons for numbers and dates, “contains”, “starts with” and “ends with” for text.
  4. Set Sort ($orderby), Paging and Total count as needed, then Run.
Query tab with the request at the top and the builder with fields, navigations and filter
The builder: choose fields, navigations and filters instead of typing.

If you prefer to type the request yourself, the workbench checks it against the metadata: “The service does not know “Name” here”, plus a suggestion such as “Did you mean ProductName?”. Below the request, one sentence says what it does – for example “Read Products with Name and Price, where Price ≥ 100, sorted by Price, at most 20”.

The result

The result view switches between Table, JSON and Fiori. In the table:

  • A click on a cell offers “Only … = …”, “Without …”, “≥” and “≤” – the filter goes into the request.
  • A column header shows its profile: how many different values, how many empty, from when to when – and “Filter on …”.
  • Load more fetches the next page. Download saves the table as CSV for Excel – with every row, even when only the first are shown.
  • Answer details shows status, duration, size and headers. Compare sets the result against the previous run: new, changed, gone.
Result table of Products with Category, above it the request as a sentence: read, including, sorted by, at most 20
The result as a table, with the request in one sentence above it.

Query as Fiori would

Query as Fiori would builds the request a Fiori elements list would derive from the annotations: the columns from UI.LineItem, the texts from Common.Text, plus units and currencies. The Fiori view then shows the result as a table with filter bar and object page – without an app.

Fiori result view: preview of a list report with filter fields and the columns from UI.LineItem
“As Fiori”: the result the way Fiori elements would show it from the annotations.

Why does Fiori not show … answers the most common question in a project: for a field, the workbench says whether it is visible in table, filter bar and object page and, if not, why – UI.Hidden set, not among the columns of UI.LineItem, not filterable, not in UI.SelectionFields. And whether users can add it themselves.

In words

Under In words you write the filter as a sentence: “price over 100 and name contains bike, the 10 most expensive”. Apply turns it into $filter, $orderby and $top. The workbench reads it from field names, labels and types – with fixed rules, without AI and without sending anything. What it does not understand, it names.

In words field with a sentence and the filter built from it
“In words”: a sentence becomes $filter, $orderby and $top.

As code

As code shows the same request as a UI5 call, for V4 services as a CAP query (cds.ql), as fetch, as cURL or as a URL – to copy into code, the console or a ticket.

Request as code dialog with the UI5 call for the current request
“As code”: the same request for UI5, CAP, fetch, cURL.

Value help

If a field has a value help (Common.ValueList), it opens in the filter as it does in the app: search values, pick one, done. The workbench queries the value help service the annotation names.

Value help for a filter field with search and results
The value help from Common.ValueList – right in the filter.

More from the result

  • Mock data turns the result into test data for the UI5 MockServer (JSON) or for CAP (CSV). With Anonymise texts, names and texts are replaced while keys and numbers stay.
  • Call an action or function lists the operations the metadata offers for this path. Take into the editor inserts the call with its parameters; you send actions like any changing request – see Changing, draft and $batch.
  • Recent requests brings back earlier queries; to keep them, use collections.

See also

Sources on this page

The superscript numbers in the text point here. Tap one to see the source right where it is used; all sources of this website are listed on one page.

  1. 1

    Query builder from the metadata ↑Product · ODataTailor product documentation, implementation plan, phase 1, query builder · checked on 2026-11-21

  2. 2

    Query like Fiori, Fiori preview, “Why does Fiori not show …” ↑Product · ODataTailor product documentation, implementation plan, phases 1 and 2 · checked on 2026-11-21

  3. 3

    $filter from natural language, without AI ↑Product · ODataTailor product documentation, implementation plan, phase 2, naturalFilter · checked on 2026-11-21

  4. 4

    “As code” and mock data ↑Product · ODataTailor product documentation, implementation plan, phases 1 and 2 · checked on 2026-11-21

  5. 5

    Value help from Common.ValueList ↑Product · ODataTailor product documentation, implementation plan, phase 1, query builder · checked on 2026-11-21

Frequently asked

Short answers.

Can the query change data by accident?
No. The Query tab sends GET requests only. Changing requests take a path of their own with preview, click and PROD lock.
Does “In words” use AI?
No. “In words” translates the sentence into a $filter with fixed rules from field names, labels and types. Nothing leaves the browser.
How does ODataTailor know which columns Fiori shows?
From the service’s annotations and the opened annotation files, above all UI.LineItem, UI.SelectionFields, UI.Facets and UI.Hidden. The workbench does not see variants and personalisation of a running app; that is what FrontTailor is for.
Which code formats are there?
UI5, fetch, cURL and the plain URL; for OData V4 also CAP (cds.ql).

Your question isn’t here? Talk to me: +43 664 1964199 office@clouddna.at Get in touch

Contact

Service stuck? Talk to us.

ODataTailor is free. If you need help – with an OData service from SEGW, RAP or CAP, with annotations for Fiori elements, with a stubborn error or for a workshop with your team – get in touch. I reply within one working day, personally.

Martin KochManaging Director, CloudDNAI read every request myself and reply personally.