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 →

Collections, comparisons, errors

A request that is right today should still be right after the next transport. So you save it, attach checks and run it on several systems – or compare the metadata straight away.

Storage
local in the browser, without credentials
Import
cURL, Postman collection
Export
Postman, VS Code REST Client, Playwright
Comparison
rows and $metadata, breaking or compatible

Saved requests

  1. Build a request and choose Save current request under Saved requests.
  2. Later, one click loads it back into the editor. It is not sent while doing so.
  3. Import takes a cURL command or a Postman collection. Export writes the collection as a Postman collection, as .http for the VS Code REST Client or as a Playwright API test.

Variables hold values that differ per system – an order number, a plant. They apply to all systems of the service or only to one. Values such as a new GUID are made up by the workbench per request.

You create Checks from the result: status, number of rows, duration, a field in the first, every or some row. After each run it says “3 of 4 met” – and what was found.

Run on several systems

Run on systems… starts a Collection run: all saved requests one after another on DEV, QAS and further systems. For each request and system the table shows rows, checks and the difference to the first system – “+2 Δ1 −0”: two only here, one changed, none missing. Below, it says how many are green. The run only reads.

Collection run with three saved requests on two clients, all green, with row differences
The collection run: every saved request on every system, with checks and differences.

One request, two systems

For a single request, Other system is enough: the same service on another system, Compare – and the rows of both systems sit side by side, with new, changed and gone.

Comparison of a request’s rows between two systems with the differences highlighted
Other system: the same query on DEV and QAS, the differences marked.

$metadata diff

Compare… sets the $metadata of the open service against another version – of the same service on another system or from a file. Each change is rated:

  • breaking – clients may fail: entity set or property removed, type or key changed, nullable stricter, MaxLength smaller.
  • compatible – something new is added, what exists stays.
  • annotation only – the data stays the same, the UI may change.
$metadata diff with breaking, compatible and annotation changes
The $metadata diff: what changed and whether it breaks clients.

Swap direction turns before and after around; Copy as Markdown puts the report on the clipboard for the transport request or the pull request.

Understanding errors

If a request fails, the workbench shows the service’s error message in readable form, not as raw JSON or XML. For SAP Gateway, the Way out follows: what the message means, which transaction helps – the error log, say – and a link that opens it in SAP GUI for HTML on this system. Copy transaction ID takes you straight to the right entry there.

Error message of a Gateway service with the way out and the transaction ID
The way out: what the error means and where to look further in the backend.

Where the time goes

Request SAP statistics asks an SAP system to send its run times along. The workbench then splits the duration: application (data provider), Gateway framework, Gateway hub, RFC between hub and backend, network and browser. Largest columns of the answer names the fields that bring the most data – with “Leave … out ($select)” as a shortcut.

Split of a request’s run time by application, Gateway and network
SAP statistics: application, Gateway, network – and the columns that make the answer large.

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

    Saved requests, variables, checks, export ↑Product · ODataTailor product documentation, ADR-008 and implementation plan phase 2 · checked on 2026-11-21

  2. 2

    System comparison and collection run ↑Product · ODataTailor product documentation, implementation plan, phase 2, system comparison · checked on 2026-11-21

  3. 3

    $metadata diff with breaking changes ↑Product · ODataTailor product documentation, implementation plan, phase 2, diffMetadata · checked on 2026-11-21

  4. 4

    Errors with a way out and SAP transactions ↑Product · ODataTailor product documentation, implementation plan, phase 2, errorAdvice · checked on 2026-11-21

  5. 5

    SAP statistics as bars ↑Product · ODataTailor product documentation, implementation plan, phase 2, “Where the time goes” · checked on 2026-11-21

Frequently asked

Short answers.

Where are my saved requests stored?
Locally in the browser, per service. There is no server and no account; to share a collection, export it as a Postman collection or .http file.
Does a collection run change data?
No. The collection run executes the saved reads. You send changing requests one by one, with preview and PROD lock.
Where do the SAP statistics come from?
From the SAP system itself: with the request, ODataTailor asks for the statistics values that Gateway sends in a header on request, and shows them. Other systems do not provide them.

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.