Hello.I set Conflict handling = “Merge conflicts” in my form, checked all documents in database to have $ConflictAction = 1.
If background agent saves the doc that opened for edit, conflict prompt appears, when user saving opened doc. Agent changes hidden fields (those, that user can’t modify).
Is there any way to make Conflict handling work as it should?
Or is there any workaround for that issue without third party tools?
Subject: Save conflict resolution is completely broken in ND6/7
First of all, your $ConflictAction field needs to be text, e.g. “1” not 1.
But ALL save conflict resolution that you describe is completely broken in ND6 and ND7, over the web and in Notes. Thankfully replication conflict resolution works properly. I’m not sure of the current status of the bug in ND8.
You can prevent save conflicts over the web by manually removing the “%%ModDate” field via JS before submitting over the web. But to what side effect is anybody’s guess…
Go report it to Lotus Support and jump on the bandwagon. I don’t remember the SPR# off the top of my head, but it’s a pretty annoying bug.
Subject: RE: Save conflict resolution is completely broken in ND6/7
Thank you for your reply Erik.I think i won’t jump. It’s sad that after two releases the bug is still here, expecially given that it’s a fracture in Notes’s backbone, and may be a reason for choice of another system.
Maybe there is a way to process conflict on OnquerySave, and merge fields. Looking for sollution.