From Advanced Merge Replication Conflict Detection and Resolution
When using the default conflict resolver and client type subscriptions, the first change written to the Publisher wins the conflict. When using the default conflict resolver and server type subscriptions, priority values are assigned to individual subscribers and changes made at the node with the highest priority wins the conflict.
This behavior occurs by default and no manual intervention is required even if conflicts occur and appear in the Conflict Viewer. The Conflict Viewer merely provides a means to view conflicts that have occurred within the retention period and manually change the outcomes.
If you require conflict resolution behavior not provided by the default resolution mechanism, you have options:
- Microsoft supplied COM-Based Resolvers
- Business logic handler
- COM-based custom resolver
- Custom Stored Procedure Conflict Resolver (Not very useful for Web Sync subscribers)
A business logic handler or custom conflict resolver would provide a means to alert when a conflict occurs and automatically resolve the conflict based on business requirements.