Conflict resolution

This content is for Spring ’26. Switch to the latest version for up-to-date documentation.

When conflict resolution is enabled in mobile configuration, the sync process can detect when the same record was changed on the server (or by another user) after your last download. During Manual synchronisation or background sync, the app can surface those clashes instead of silently overwriting data.

How it works

While syncing, the app compares record versions against what was last confirmed on the device.
If conflicting changes exist, the sync UI can list the fields in dispute.

User experience

Conflict resolution is off by default unless your administrator enables it.
When a conflict is shown, you can choose which version should win for each element so the outcome is explicit.

The option you confirm becomes the basis for the merged record going forward, subject to server validation.