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 →

Capture

What does the app actually send to the backend? The “ODataTailor” panel in DevTools records it – any Fiori, UI5 or other web app, without changing it. The workbench turns it into a picture.

Where
DevTools panel “ODataTailor”
Detects
OData V2 and V4, also parts inside $batch
Storage
in memory only, at most 500 requests
Secrets
redacted while recording, cookies dropped

Record in the DevTools panel

  1. Open the app, open DevTools (F12) and choose the ODataTailor tab.
  2. The OData capture runs at once. Pause pauses, Record resumes, Clear starts over.
  3. Work in the app. On the left are the detected Services with the number of requests, failures and whether their $metadata was captured; on the right each request with method, status, duration and size. Parts of a $batch are listed one by one.
  4. A click on a request shows headers and bodies. Filter by URL narrows the list.
ODataTailor DevTools panel with the detected services and the requests of a Fiori app
The “ODataTailor” panel: services on the left, requests on the right, $batch split into its parts.

Hand over to the workbench

  • Open in workbench opens the service with the captured $metadata and the calls. The app’s annotation files go along.
  • Query in workbench takes a single request into the Query tab – to reproduce and change it.
  • Live to workbench keeps sending new calls over while you click in the app.
  • Export saves the capture as a file (.odtrace) or as data for the UI5 MockServer, optionally with anonymised texts.

Calls in the diagram

In the workbench the captured Calls appear above the diagram. “Previous call” and “Next call” step through them; the diagram highlights which types and navigations a call touches and which fields it loads, filters and sorts. Each call carries its role in the app: list, object page, value help, count, draft step, side effect.

Workbench with a captured call, highlighted types in the diagram and the call list
Calls in the diagram: each request with its role, the types it touches and the fields it loads.

Play runs through the capture – step by step or at the pace of the app. Time line shows all calls as bars over time. Query in workbench puts a call into the query.

All together

All together lays all calls on top of each other: which types the app reads and changes, and how many of the loaded fields it uses – “18 of 64 fields used”. Fields that are loaded but shown nowhere according to the annotations are listed separately. Copy $select gives the field list that is really needed.

All calls together as a heat map on the diagram, edges weighted by use, the summary per type on the right
All together: what the app reads, changes and really needs.

Better this way

The workbench spots patterns that cost time: the same call twice, a wide type without $select, many single reads by key, a navigation loaded after reading. Better this way suggests the replacement – one $filter instead of ten single reads, one call with $expand instead of three, only the fields in use.

Better this way suggestion with the measurement before and after
“Better this way”: the suggestion and the measurement of both variants.

Measure both runs the old and the new variant and gives time, data and number of calls, before and after. Measuring only reads.

Save and compare captures

Save capture as file keeps a state – before an optimisation, say. Compare with capture file… sets two states side by side: calls, HTTP requests, time, data, changing calls and hints, plus each kind of call with new, gone, faster, slower. Save reads as requests turns the capture into a collection you can run on other systems.

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

    Capture in the DevTools panel, redacted ↑Product · ODataTailor product documentation, ADR-009 · checked on 2026-11-21

  2. 2

    Calls in the diagram, overview, “Better this way” ↑Product · ODataTailor product documentation, ADR-009, implementation plan phase 2 · checked on 2026-11-21

  3. 3

    No credentials, tokens or cookies stored ↑Product · ODataTailor product documentation, CLAUDE.md, ADR-005, ADR-007 and ADR-008 · checked on 2026-11-21

  4. 4

    What only FrontTailor can do on the running app ↑Product · FrontTailor ADR-050 (21 November 2026) · checked on 2026-11-21

Frequently asked

Short answers.

Does capture only work with SAP Fiori?
No. The panel detects OData V2 and V4 in any web app, including your own UI5, React or Angular apps. The workbench recognises Fiori-specific roles such as object page or value help from the annotations.
Does the capture change the app?
No. The panel reads the network traffic seen by DevTools and does not interfere with the page.
What happens to tokens and cookies in a capture?
Cookies are dropped; secret headers and secrets in URLs and bodies are replaced while recording. The capture stays in memory until you explicitly save it as a file.
Does capture work in Firefox too?
Yes. The “ODataTailor” panel is available in the developer tools of Chrome, Edge and Firefox.

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.