Cause of document conflict

HCL Domino Domino Forum
1

In rare cases, my users are experiencing document conflicts.

I am unable to track down the cause but suspect it may be due to the form design.

The doc locking is enabled there are no local replicas so that 2 people can never have the same doc opened for edit.

What other reasons can there be for document conflicts to occur?

2

Subject: Cause of document conflict

There are several ways I can think of that could cause this behavior:

  1. The user has managed to open the same document in 2 different tabs in the Notes interface. Usually this won’t occur but it is possible using LS to open the same document multiple times. Edit and save each tab and you can generate a Rep Conflict.

  2. There is code somewhere in your form which programatically saves the document while it’s open. i.e. calling the Save method of NotesDocument during the QuerySave might under the right circumstances cause your conflict.

  3. As someone else mentioned a scheduled agent updating the document at the same time the user is making a manual change.

  4. Some kind of “admin” function that allows certain users to update a document at any time.

This is just a start off the top of my head.

3

Subject: Cause of document conflict

The doc locking will prevent save conflicts but not replication conflicts.

  1. User A on Server A edits, saves and closes a document.

  2. User B on Server B edits, saves and closes the same document.

  3. Replication occurs.

Bang - you have a replication conflict.

4

Subject: RE: Cause of document conflict

There is only 1 database in 1 server.

Basically 2 users can never open the same doc at the same time (LN would not allow it).

I get about 3 cases (the view shows a “save or replication conflict”) in about 300 files in 2 months of heavy updating.

I am wondering if somewhere in the form there is a code is causing the conflict.

Is there a condition where doc.save can cause conflict (when the doc is in a certain state?)

5

Subject: RE: Cause of document conflict

The only thing I can think of is scheduled agents updating documents.

I am not sure here but I think the document locking will only affect users, not agents.