Overview
Optimistic Concurrency
Optimistic concurrency prevents overwriting concurrent modifications on the same record.
During updateRecord, the server compares the original values (__original) with the current DB state:
- if the values match, the update proceeds;
- if they do not match, the update is blocked with an optimistic concurrency error.
With the delta payload, the check is applied only to modified fields (plus dedicated handling for multiple_check fields).
AppSetting
The feature is controlled by AppSettings.optimisticCheckEnabled.
Snippet 1JSON
"AppSettings": {
"optimisticCheckEnabled": "true"
}Values:
"true": check active (recommended)."false": check disabled.
Operational Notes
- In case of conflict, the save is rejected to prevent lost updates.
- In inline editing + batch save, the check is evaluated at the time of batch persistence.
- For many relationships (many-to-many/multi-select), the comparison uses the current ID set vs the original.