Dear All,
Now a days we generally faced problem like missing document due to Replication , so in Form proprieties we just select “Merge Conflict” but still we have problem and i ma not able to found any better solution for this, So any one can help me for solve this type of problem.
Subject: Replication Conflict Document Problem
Merge Conflicts will still generate replication/save documents if two users update the same field; merge only works if the users update different fields.
Are you having replication problems (db content is different in two different dbs) or are you creating rep/save (black diamond) document? Both problems have ‘replication’ in their name but are different issues.
If you can provide more detail we may be able to provide more help.
Subject: Replication Conflict Document Problem
It takes more than just setting the property to solve replication conflict issues. That setting causes any new or edited documents to be marked with a $ConflictAction item, which is what tells the replicator what to do (i.e., in your case, merge). But existing documents do not have that item, and if the conflicts aren’t being directly caused by users editing the document with the updated form, but rather by an agent or some other process updating them, that item will not be added. Furthermore, in order for the $ConflictAction item to really be effective, it must exist in both replicas. So in order to really implement it effectively, what you have to do is (a) set the form property, (b) delete all replicas of the database except for one, (c) run an agent to set $ConflictAction to the appropriate value (1, 2, or 3, if I recall correctly) in all existing documents, and (d) create new replicas to replace the deleted ones.
And even if you do that, what Doug mentioned remains true. $ConflictAction only stops the replication task from creating conflicts. It doesn’t stop save conflicts that occur when users (or other server tasks) make overlapping changes within the same server.
-rich