I heard there is some cooler ways to prevent rep/save conflict in R6 OTHER THAN "merge replication conflict" in form properties. How effective is this ?
Forget about R6 for a moment, even in R5 -
Is there any way to RE-WARN and LOG IN HISTORY field the merging of documents after the replication/save warning is prompted to the user and 'Yes' is clicked ?
Pl, feel free to suggest any other method also to prevent rep /saves conflict. I have used locking/unlocking of document in the past but it is not that effective. We still get rep/saves may be due to some network glitch or backend documents saves or partial saves. We are running our applications on only one server. It do replicate but with a read only replica of the db in another zone server. So there is no way changes are coming from the other server.