I have a database that’s getting replication conflicts in the $UpdatedBy and $Revision field from a foreign server in our company. There’s a lot more entries in these fields vs here in the us. Why the foreign servers say they are modifying the document I don’t know.
I thought about modifying the advanced db properties to limit the $UpdatedBy and $Revision to say 20 entries and turn on Merger Replication Conflict for the main form in the db.
Question will the aboves actions most likely clear my conflicts? Also is there any detriment to enabling this features?
Subject: Advanced setting limit $Updated and $Revision and replication conflict
I think it’s a great idea to limit the entries in those fields. The downside would be if you wanted to go back 30 entries to see who/when modified the document, you wouldn’t be able to. For most apps, this is an unlikely scenario.
I don’t think this setting will be relevant for your rep/save conflicts. Those may be mitigated with “merge” turned on at the form level, but if it’s humans, not agents, that are modifying the documents, then it’s unlikely to truly help.