Multiple users can simultaneously edit the same document in one copy of a database or edit the same document in different replicas between replication sessions. When these conditions occur, Domino® stores the results of one editing session in a main document and stores the results of additional editing sessions as response documents. These response documents have the title Replication or Save Conflict.

Domino uses the $Revisions field, which tracks the date and time of each document editing session, to determine which document becomes the main document and which documents become responses.

Replication conflicts

A replication conflict occurs when two or more users edit the same document and save the changes in different replicas between replications. These rules determine how Domino saves the edit sessions:

• The document edited and saved the most times becomes the main document; other documents become Replication or Save Conflict documents.
• If all of the documents are edited and saved the same number of times, the document saved most recently becomes the main document, and the others become Replication or Save Conflict documents
• If a document is edited in one replica but it is deleted in another replica, the deletion takes precedence, unless the edited document is edited more than once or the editing occurs after the deletion.

A save conflict occurs when two or more users open and edit the same document at the same time on the same server, even if they are editing different fields. When this situation occurs, the first document saved becomes the main document. Before the second document is saved, a dialog box indicates that the user is about to save a conflict document and if the user saves the document, it becomes a Replication or Save Conflict document.

Note: ACL and design changes never result in replication or save conflicts; the most recent change always prevails.

Preventing replication or save conflicts

The following techniques reduce or eliminate replication or save conflicts.

A database designer can do the following:

• Select the Form property Merge replication conflicts to automatically merge conflicts into one document if no fields conflict. This applies to replication conflicts only and not to save conflicts.
• Specify a Form property for versioning so that edited documents automatically become new documents.
• Lock documents in a database. For additional information, see Document Locking in the related information.

• Assign users Author access or less in the database ACL to prevent users from editing other users' documents.
• Keep the number of replicas to a minimum.
• If the database property Limit entries in $Revisions fields is set to a value greater than 0, increase the limit by specifying a greater value than the existing one or specify -1 to remove the limit.

Related concepts
Monitoring replication of a database

Related tasks
Consolidating replication or save conflicts
Configuring a database ACL

Help on Help

All Help Contents

Help on Help