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 →

Changing, draft and $batch

Changing data is the part where something can break. So ODataTailor sends nothing that changes data without a preview and a click – and to a production system nothing that changes data at all.

Methods
POST, PUT, PATCH, MERGE, DELETE
Check
body against the metadata, before sending
Protection
confirmation, PROD lock in the background, fail-closed
$batch
multipart (V2 and V4), JSON batch (V4.01)

Send a changing request

  1. In the Query tab, switch the Method – or choose Edit in a result row; then path and key are already set.
  2. Template from metadata fills the Body (JSON) with every field of the type and fitting sample values. Under Deep insert you include navigations.
  3. While you type, the workbench checks the body: unknown fields, wrong types, too long, required field missing, key changed. Each error comes with a suggestion.
  4. Load ETag fetches the current ETag into If-Match (ETag). More headers takes headers of your own.
  5. Send… shows the request once more with host and method. Only Send now sends it.
MERGE request on Products with a checked body and the confirmation dialog with If-Match and the CSRF note
Changing with a safety net: body from the metadata, checks while typing, confirmation before sending.

ODataTailor fetches the CSRF token itself when sending and adds it; it is never stored. The response shows status, duration, body and headers – sent and received. Read the record then opens the changed record in the query.

The PROD lock

Changing requests are never sent by the workbench itself but by the extension’s background. Before each send it checks whether the target is a production system – via the Production switch in the “Systems” dialog or from the company policy. If it is, or if that cannot be determined, it sends nothing: “Blocked: … is a production system. Nothing was sent.”

Working with drafts

RAP and CAP services with draft do not change data directly but through a draft. ODataTailor walks through the steps Fiori takes too:

  1. Choose Edit as draft in the result row.
  2. Create draft – the service creates the draft and locks the active record.
  3. Change draft – set fields of the draft with PATCH.
  4. Prepare (optional) – the service’s checks run without activating.
  5. Activate – the draft becomes the active record. Or Discard draft: the active record stays as it was.
Draft flow with the steps create, change, prepare, activate
The draft flow step by step – each step on its own, with its answer.

Drafts and locks reads all drafts of an entity set with who holds them: who locked which record, since when, and which drafts have lost their lock. That settles “Who is holding my record?” without going to the backend.

$batch composer

  1. Prepare a request and choose Add to $batch. Reading and changing requests can be mixed.
  2. Set the order in the $batch composer. Same change set as before groups changing requests into a change set that applies in full or not at all.
  3. With $ and the Content-ID, a request refers to the result of an earlier one – a header just created, say.
  4. Choose the Format: Multipart (V2 and V4) or JSON batch (V4.01). Show request shows the finished body; Send… and Send now send it.
$batch composer with GET, MERGE and POST, the two changing ones in change set 1, the multipart request below
The $batch composer: order requests, build change sets, check the finished request.

The answer is listed per part with its status. “Worst part” shows at a glance whether something went wrong; if a change set fails, it says so as a whole.

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

    Changing requests with checks ↑Product · ODataTailor product documentation, implementation plan phase 2 and ADR-007 · checked on 2026-11-21

  2. 2

    PROD lock, fail-closed ↑Product · ODataTailor product documentation, ADR-007 and manifest (managed_schema) · checked on 2026-11-21

  3. 3

    Guided draft flow ↑Product · ODataTailor product documentation, implementation plan, phase 2, draft · checked on 2026-11-21

  4. 4

    $batch composer ↑Product · ODataTailor product documentation, implementation plan, phase 2, $batch · checked on 2026-11-21

Frequently asked

Short answers.

Can ODataTailor change something on PROD by accident?
Not if the system is marked as production or listed in the policy: the extension’s background blocks every changing request there, even when in doubt. On top of that comes the confirmation with host and method before each send.
Does ODataTailor store the CSRF token?
No. It fetches the token when sending, puts it into the request and discards it afterwards.
Does the draft flow work with OData V2?
Yes, if the service offers draft – a Gateway service generated from CDS with SADL and draft, say. The steps have the same names; the workbench calls the operations that fit the version.

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.