Sources.
“Low-code.” “Zero effort.” “Fully automated.” – developer tools promise a lot and prove little. For a tool that checks every request against the metadata, that would be embarrassing. So every claim on this website has a source: product claims with our product documentation as of pre-release 0.1.0, as of 21 November 2026, standards, books and vendor with link and date.
All siblings of the Tailor family share the habit. For us it means: no body left unchecked1, no claim without evidence.
Product
Pre-release 0.1.0 of 21 November 2026
The extension carries version 0.1.0. It is built and tested but not yet submitted to any store. Until then it is available on request as a package to load.
ODataTailor product documentation, manifest and implementation plan · checked on 2026-11-21
Browser extension for Chrome, Edge and Firefox
One codebase, Manifest V3, builds for Chrome, Microsoft Edge and Firefox. Requirement: Chrome or Edge from version 137, Firefox from 140. User interface in German and English, light and dark.
ODataTailor product documentation, README and build configuration · checked on 2026-11-21
Free, no account and no licence
ODataTailor is free like AuthTailor: no editions, no paid features, no sign-in inside the extension. Anyone who needs the workbench on the running Fiori app finds it in FrontTailor.
Product owner decision of 21 November 2026 · checked on 2026-11-21
Grown out of FrontTailor, same packages
The parser, annotation catalogue, $batch, error analysis and the graphical metadata explorer come from FrontTailor. They live in shared packages (odata-core, odata-explorer, odata-workbench) that both ODataTailor and FrontTailor use.
ODataTailor product documentation, ADR-001 and ADR-010 · checked on 2026-11-21
What only FrontTailor can do on the running app
In FrontTailor the same workbench is the full view of the OData module. On top comes what only works on the running UI5 app: the UI action behind each call from the recorder, the bound controls of a type, “Jump to control” and the annotation explorer. Reading is part of the Community edition there; changing, $batch, collections and the $metadata comparison belong to Pro.
FrontTailor ADR-050 (21 November 2026) · checked on 2026-11-21
Screenshots with made-up data
Every image on this website shows the real extension. A script takes them against a mock SAP Gateway that runs only on the local machine (localhost), with made-up products, categories and orders.
ODataTailor product documentation, screenshot script e2e/shots · checked on 2026-11-21
Open a service: URL, catalogue, file
Via the service URL with the browser’s sign-in, from the SAP Gateway system catalogue (V2 and V4, all pages, with search, favourites and “recently opened”) or as a file: EDMX ($metadata and annotations) and CSDL JSON via dialog, drag and drop or a sample. Annotation files of a V2 service come along from the catalogue. If the session has expired, the workbench offers “Sign in in a tab”.
ODataTailor product documentation, implementation plan, phases 0 and 1 · checked on 2026-11-21
Diagram with path finder and explained annotations
All types as a diagram with focus, a path finder for $expand and export. Annotation markers sit in fixed columns; a click on a marker or chip (HeaderInfo, LineItem, SelectionFields …) opens an explanation, the position in the collection, the values and the link to the vocabulary. Measured: 1,000 types stay fluid.
ODataTailor product documentation, implementation plan, phase 1, diagram · checked on 2026-11-21
Service profile and metadata browser
The profile sums up a service (version, sets, types, operations, annotations) and can be copied as Markdown. The metadata browser searches all types, properties and annotations.
ODataTailor product documentation, implementation plan, phase 1, workbench · checked on 2026-11-21
Query builder from the metadata
Entity set, $select, an $expand tree up to three levels with $select per navigation, conditions, sorting, paging; the URL stays freely editable, with syntax highlighting and pretty print. The query is also spelled out as a sentence, and “Did you mean …?” checks before sending. From the result: the column header sorts, the cell menu filters, a column profile shows the most frequent values, a comparison with the previous run, CSV.
ODataTailor product documentation, implementation plan, phase 1, query builder · checked on 2026-11-21
Query like Fiori, Fiori preview, “Why does Fiori not show …”
“Query as Fiori would” builds the request of a list report: columns from UI.LineItem, sorting from UI.PresentationVariant, filter fields from UI.SelectionFields, 20 rows with count. The “Fiori” view shows the list report and object page from the result, without a request of its own. “Why does Fiori not show …” explains per field from the annotations (UI.Hidden, FieldControl, LineItem, TextArrangement, filterability, facets) whether the table, filter bar and object page show it. Results are formatted as in Fiori: units and currencies, dates, text for the code.
ODataTailor product documentation, implementation plan, phases 1 and 2 · checked on 2026-11-21
“As code” and mock data
“As code” writes the query for UI5 (V2 read, V4 bindList/bindContext with Filter and Sorter), CAP cds.ql, fetch, cURL and as a URL. Mock data from the result comes as a UI5 MockServer file and as a CAP CSV; texts are replaced with pseudonyms by default.
ODataTailor product documentation, implementation plan, phases 1 and 2 · checked on 2026-11-21
$filter from natural language, without AI
“In words” reads German and English by rules from field names, labels and types: comparisons, text (contains, starts with), “between … and …”, dates like “30 days ago”, sorting (“the 10 most expensive”) and row limits. Preview of the understood and the not understood words. Without AI and without a request.
ODataTailor product documentation, implementation plan, phase 2, naturalFilter · checked on 2026-11-21
Value help from Common.ValueList
When filtering, the query builder offers the value help described by the Common.ValueList annotation (same service, InOut and Out parameters, the first 100 values).
ODataTailor product documentation, implementation plan, phase 1, query builder · checked on 2026-11-21
Changing requests with checks
POST, PUT, PATCH, MERGE (V2) and DELETE. The JSON body gets a template from the metadata and is checked against it: types, Nullable, MaxLength, unknown fields, mandatory fields, keys. If-Match comes from the record or via “Load ETag”; the extension fetches the CSRF token itself and keeps it in memory only. Nothing is sent before preview and click. Plus actions and functions from the metadata and deep insert.
ODataTailor product documentation, implementation plan phase 2 and ADR-007 · checked on 2026-11-21
Guided draft flow
For V4 draft roots (Common.DraftRoot): create the draft, change it, prepare, activate, and discard at any time – each step its own request with preview and click. “Drafts and locks” shows who holds a draft and since when.
ODataTailor product documentation, implementation plan, phase 2, draft · checked on 2026-11-21
$batch composer
Collect requests from the editor, reorder them, form change sets as UI5 does, check $n references; multipart (V2/V4) or JSON batch (V4.01). Responses appear per part with status, SAP error message and the failed change set.
ODataTailor product documentation, implementation plan, phase 2, $batch · checked on 2026-11-21
PROD lock, fail-closed
Changing requests and every $batch go only through the extension’s background. It first checks whether the system is marked “Production” in the “Systems” dialog or listed in the IT’s prodHosts policy, and then blocks. If it cannot tell, it does not send. The workbench page itself sends only GET.
ODataTailor product documentation, ADR-007 and manifest (managed_schema) · checked on 2026-11-21
Saved requests, variables, checks, export
Requests per service, relative to the service root, without secrets. Variables per service and per system, plus dynamic values such as a fresh GUID per send. Checks on status, row count, duration and field values after every run. Import from cURL and Postman, export as a Postman collection, as .http and as Playwright tests.
ODataTailor product documentation, ADR-008 and implementation plan phase 2 · checked on 2026-11-21
System comparison and collection run
“Other system” runs the request on the same service of another system or client and compares row by row via the key: only here, changed, only there. “Run on systems…” runs every GET request of a collection on several systems and shows a matrix with status, rows, duration, checks and differences. GET only.
ODataTailor product documentation, implementation plan, phase 2, system comparison · checked on 2026-11-21
$metadata diff with breaking changes
“Compare…” in the profile against another service, a service URL on another system or a file. Classified as breaking (removed, type changed, shorter MaxLength, Nullable becomes false, new mandatory property, key, cardinality …), compatible or annotation only; report as Markdown.
ODataTailor product documentation, implementation plan, phase 2, diffMetadata · checked on 2026-11-21
Errors with a way out and SAP transactions
From the OData error and the authorization diagnosis, the likely cause with the matching transactions – SU53/PFCG, /IWFND/MAINT_SERVICE, SICF, SM59, SEGW/SE24, ST22, SMICM, /IWFND/ERROR_LOG, /IWBEP/ERROR_LOG – which open with a click in SAP GUI for HTML on the same system and client. Transaction ID to copy.
ODataTailor product documentation, implementation plan, phase 2, errorAdvice · checked on 2026-11-21
SAP statistics as bars
“Request SAP statistics” sends sap-statistics: true on click and shows application, Gateway framework, hub, RFC overhead and network as bars; otherwise W3C Server-Timing. Plus the largest columns of the response with “leave out ($select)”.
ODataTailor product documentation, implementation plan, phase 2, “Where the time goes” · checked on 2026-11-21
Capture in the DevTools panel, redacted
The “ODataTailor” DevTools panel reads calls through devtools.network, in Chrome and Edge without any further permission. It recognises OData in any web app, redacts headers, URL parameters and $batch bodies while recording and keeps at most 500 requests in memory. “Open in workbench” hands over $metadata and calls without a new network call. Captures can be saved as .odtrace and compared.
ODataTailor product documentation, ADR-009 · checked on 2026-11-21
Calls in the diagram, overview, “Better this way”
The app’s calls can be stepped through in the diagram, $batch parts one by one. Every call gets its role (value help, table page, object page, side effect, draft step …). Hints on single reads, duplicates and missing $select; the “All together” view shows a heat map with an $select suggestion per type and fields that are loaded but never shown. “Better this way” suggests $filter … or …, $expand and $select; “Measure both” runs both variants on click (GET only).
ODataTailor product documentation, ADR-009, implementation plan phase 2 · checked on 2026-11-21
No server, no telemetry, nothing from third parties
ODataTailor has no CloudDNA server, no telemetry and no analytics. Fonts, themes and locale data ship with the extension, not from the UI5 CDN. An automated test checks on every build that the workbench makes no request to third parties.
ODataTailor product documentation, ADR-003 and end-to-end test “no request to third parties” · checked on 2026-11-21
No network call without a visible request
The extension only calls a service when you open it, send a query or press a button such as “Request SAP statistics” or “Measure both”. The live mode of “As code” has to be switched on explicitly.
ODataTailor product documentation, ADR-003 · checked on 2026-11-21
Permissions: storage, host access per system
Only storage is fixed in the manifest, plus the DevTools page for capture (Firefox: implicitly devtools). Host access is optional (https and http) and requested per system on click; the “Systems” dialog lists every granted system and revokes it. No content script.
ODataTailor product documentation, manifest (wxt.config.ts), ADR-004 and ADR-009 · checked on 2026-11-21
No credentials, tokens or cookies stored
The extension uses the browser’s sign-in; it never asks for a password. Credentials, tokens and session cookies go neither into storage nor into exports or collections; variables that look like secrets are rejected. The CSRF token lives in memory only. Response headers appear without cookies and tokens.
ODataTailor product documentation, CLAUDE.md, ADR-005, ADR-007 and ADR-008 · checked on 2026-11-21
Workspace only locally in the browser
Opened services, history, favourites and saved requests live in the browser’s IndexedDB and storage.local. None of it goes to CloudDNA. Uninstalling deletes everything.
ODataTailor product documentation, ADR-005 · checked on 2026-11-21
Standard
OData – a standard of OASIS Open
OData (Open Data Protocol) describes REST APIs with metadata ($metadata, CSDL), query options such as $filter, $select and $expand, and $batch. Version 4 is a standard of OASIS Open; SAP Gateway, RAP and CAP serve OData V2 and V4. Annotations such as UI.LineItem come from the OASIS and SAP vocabularies.
odata.org, documentation · checked on 2026-11-21
Vendor
CloudDNA GmbH – SAP Silver Partner
CloudDNA describes itself as an SAP BTP partner from Austria for the DACH region and an SAP Silver Partner; it supports SAP projects in Austria, Germany and Switzerland. Focus areas according to its website: integration, architecture and clean core, Fiori and UX, full-stack development, agility and DevOps, and training. Martin Koch is listed there as founder & managing director and SAP Champion.
clouddna.at, start page and team · checked on 2026-11-05
Books on SAP Fiori elements, SAPUI5 and full-stack development
Rene Glavanovits, Martin Koch, Daniel Krancz and Maximilian Olzinger: “SAP Fiori Elements” (German and English), “SAPUI5 – The Comprehensive Guide” and “Full Stack Development with SAP” (“Fullstack-Entwicklung mit SAP”), all at SAP PRESS, Rheinwerk Verlag.
Rheinwerk Verlag (SAP PRESS), search “martin koch” · checked on 2026-11-05
FrontTailor – developer tools for SAP Fiori and UI5
CloudDNA’s browser extension for SAP Fiori and UI5 apps: inspector, models, OData console, performance, quality check, annotation explorer and operations on the running app. Its OData parts are the foundation of ODataTailor.
fronttailor.com · checked on 2026-11-21
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
Changing requests with checks ↑Product · ODataTailor product documentation, implementation plan phase 2 and ADR-007 · checked on 2026-11-21