Skip to content

Optimistic Locking in Offline Apps #11218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ConnorLand wants to merge 2 commits into
base: development
Choose a base branch
from
+11 −3
Open

Optimistic Locking in Offline Apps #11218

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0f71bc5
add app type support section to OL doc
ConnorLand May 19, 2026
103d954
redo offline info per SME feedback
ConnorLand May 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions content/en/docs/refguide/runtime/optimistic-locking.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,17 +17,25 @@ If a conflict is detected—meaning someone else has modified the data since you

You can decide whether optimistic locking is enabled or disabled for your app.

## Behavior of App with Optimistic Locking Disabled
### Support Status by App Type

Optimistic locking is supported in the following types of Mendix apps:

* Online apps: supported since [Studio Pro 11.5](/releasenotes/studio-pro/11.5/)
* Offline apps: supported since [Studio Pro 11.11](/releasenotes/studio-pro/11.11/)
* **Additional Information on Optimistic Locking in Offline Apps** — As data can live for a long time in offline apps, changes based on that data that are synchronized from offline apps to the Mendix Runtime Server are committed to the database without optimistic locking to avoid conflicts. As such, offline data synchronization may overwrite changes.

## App Behavior: Optimistic Locking Disabled

When two modifications are saved, they are applied in the order of processing. Only changed attributes are written to the database. This means that if the two commits change different attributes or associations of an object, the changes are not overwritten.

For example, if one user commits changes for `AttributeA` and `AttributeB` and another user commits changes for `AttributeB` and `AttributeC` for the same object, then both `AttributeA` and `AttributeC` are committed according to both users' changes. `AttributeB` is committed based on whichever change was committed later.

## Behavior of App with Optimistic Locking Enabled
## App Behavior: Optimistic Locking Enabled

The Mendix runtime implements optimistic locking by tracking the version of all objects using the attribute `MxObjectVersion` with type `Long`. Although the `MxObjectVersion` attribute is not write-protected, setting this value does not result in it being saved to the database. Its current value is compared with the value for the same object in the database.

### How to Enable and Use Optimistic Locking
### Enabling and Using Optimistic Locking

You can enable optimistic locking for your Mendix application in the `Runtime` tab in the **App Settings** dialog:

Expand Down