as a second fyi…
We have been having replication conflict issues while settting up a third party contact management solution to our notes environment. The issue had stumped us for quite a while as no fields in the two reps where changed, until the following was brought to our attention. I could not find much in the KB on this, so I would like to mention this again for anyone who think they are having issues like this. In our case, the conflicts were in the PNABs that we were setting up…
If you open a contact on a local PNAB and simply save and close it witout even making a change, then if someone does the same thing on a different replica and the screen is somehow different than the the first persons, (maybe they adjust the view pane or the navigation bar). When they replicate, there will be a conflict. In our case, it was the comments field.
We are running 6.5.4. IBM, I hope you fix this as this will happen an any RTF.
Below is the only thing related to this on the site. If there is more info on this, please let me know.
Be aware that having Rich Text fields in a form will cause replication conflicts when two users change the document regardless of which fields were updated - in effect, a false positive. I do not know if this was addressed in R7 but, it still existing in early R6 versions.
If you have Rich Text fields, reevaluate if you need you can change them to normal Text fields.
Also, convincing users to replicate often will also reduce conflicts.
On the issue of an automated agent, the only way to do this reasonably and not throw out proper changes is to build an conflict resolution tool for an Admin that looks at every field of consequence in the two documents (main and conflict) and presents the fields that are different and their values. It then needs to allow the Admin the ability to pick the correct value and store these choices in the main document as an update . . . it helps but, will not reduce conflicts to 0.