Conflict Detection

When an approver approves a submission the system checks for conflicts between the staged changes and the current state of the live data:

• Edit conflict — A record that was edited in the submission has been changed in the live data since the submission was created. A warning is shown but the approval proceeds; the staged value takes precedence.
• Delete conflict — A record that was marked for deletion has been modified in the live data since the submission was created. A warning is shown; the deletion still proceeds.
• Insert duplicate — A new record in the submission has a Code that already exists in the live data. The duplicate row is automatically skipped and reported; the remaining rows are still approved.

Conflict warnings are listed in the approval result summary so the approver is aware of any data that may need a follow-up review.