A Script A Rest (SAR) call to an action requiring a precondition (If-Match/ETag) header fails with `ODP_MISSING_PRECONDITION` (428), even though the same call works fine in Postman with the header manually supplied, and SAR only exposes one header parameter slot.

All FAQ questions / Integrations and APIs

Answer

In SAR, the If-Match header is populated automatically from the object referenced by the Using keyword — check that the specific result object you're passing via Using actually contains an @odata.etag property (from a preceding read/read-result step), since a missing etag on that referenced object is what produces exactly this precondition-missing error. Running the script with the LogLevel=diag command-line argument surfaces the actual outgoing request headers, which is the fastest way to confirm whether the etag is really being sent.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions