Hi
My Self Amar Kumar Das and i have in Lotus notes last 14 yrs but last 3 year i have faced one main issue that is save conflict , my application is purely Client based application and it is replicated in 30 server
So last year every time i have facing save conflict document which disappear my booking document so that user not see this document in mian view so that issue come
For this i have apply Set Form Prop “Merge/No Conflict” option which is before only Mege Conflict, so after that we solve this case around 80% but still some case it show Merge Conflict
So can any one help me how to solve this case 100% …
Subject: Couple more things…
What is your replication schedule for this database?
Also - in Database Properties - what is the value on ‘Limit entries in the $Revisions field’ ?
Like Mike indicated - there are many different issues that can cause replication of save conflicts to appear.
One thing I found while fighting a similar issue is the ‘save’ conflict - which can be prevented by the user. If a user opens a document and modifies it, when they click save they will receive a pop-up message “Another copy of this document was saved while you were editing it. Save your changes also as a Save Conflict document?” If they choose to ignore the warning and save their change, a save conflict document is created.
So, user education may help. You might also be able to include some code to check for backend document changes to help prevent the user from creating save conflicts.
We upped the replication schedule for our highly modified databases, and in some cases we limited the number of replicas.
Subject: Save conflict Issue
Dear Mike,
Yes that is the Big challenge for in Lotus notes if this was solved then Lotus notes 70% problem will be solved , so if any other solution then let me know
Subject: Save conflicts during merges come from 2 places.
First, the save conflict can still occur. Merging only happens during replication.
Second, the save conflict can occur while merging documents when a single field is edited on both servers.
The solution is never easy: you can write an agent to check for differences first, then if the difference either doesn’t exist (might be the same change on 2 servers) or is irrelevant, just delete the rep conflict.
If the change is significant – it’s got to be rewritten & modified again. And I’d highly suggest it be replicated back the moment you have a merged doc, because trying to merge merges is messy.