Loading

Before-Save Flow (API v66+) Throws INVALID_FIELD_FOR_INSERT_UPDATE on Field Update When Called from an Unsupported API Version

Udgivelsesdato: Jul 16, 2026
Beskrivelse

Starting with Spring '26 (Flow API version 66), before-save record-triggered flows that attempt to update fields will fail with the error INVALID_FIELD_FOR_INSERT_UPDATE: Invalid target field for field update when the initiating API call uses an API version older than the version in which the target field was introduced.

This is expected behavior and not a bug. Starting with Flow API v66, the platform enforces version-specific metadata and field accessibility constraints at the commit layer — meaning a flow can no longer write to a field that wasn't accessible in the API version used by the calling client.

Example: If a field was introduced in API v46 (Summer '19), any REST API call made at v45 or earlier will trigger this error when a before-save flow (v66+) attempts to update that field.

Spring'26 flow version updates.

 

"Record-triggered flows that run before records are saved now respect the internal writeable status of non-insertable fields. If existing flows try to update fields that aren’t editable, this error message appears: Invalid target field for field update."

 

Example Fields (introduced in API v46 / Summer '19):

  • UserPreferencesReceiveNoNotificationsAsApprover
  • UserPreferencesReceiveNotificationsAsDelegatedApprover

 

Symptoms

You may observe one or more of the following:

  • Before-save record-triggered flows (v66+) throw the error: Invalid target field for field update (errorCode: INVALID_FIELD_FOR_INSERT_UPDATE) when updating a field via a REST API caller
  • The error occurs during record updates via a REST API caller using a version older than when the field was introduced, but not during:
    • Record inserts (creates) via the same integration
    • Manual UI updates
    • REST API calls using a version equal to or newer than the field's introduction version
  • The issue began after upgrading the flow to API version 66 (Spring '26)
  • Reverting the flow API version to 65 or below resolves the error
  • The flow executes successfully in-memory; the error is thrown at the platform commit layer post-flow execution

Root Cause

Prior to Flow API v66, before-save flows could update fields regardless of whether those fields were accessible in the calling client's API version. This was a platform-level security/access bug.

Flow API v66 (Spring '26) introduced a fix that added an explicit check: if a field is not accessible in the API version used by the calling client, the platform will reject the write at the commit layer with INVALID_FIELD_FOR_INSERT_UPDATE. The fix is API-versioned, meaning it only applies when the flow is running at v66 or higher.

Løsning
  • Option 1 — Upgrade the API caller version (Recommended) Update the REST API caller to use a version equal to or newer than the API version in which the target field was introduced. For fields introduced in Summer '19, this means upgrading to v46.0 or later.
  • Option 2 — Downgrade the flow API version to v65 or lower (Temporary workaround — not recommended long term) Reverting the flow to API v65 or below will restore the previous behavior. Note that this re-introduces the pre-fix behavior and is not a sustainable solution.
Vidensartikelnummer

005389121

 
Indlæser
Salesforce Help | Article