Assembly: Microsoft.Synchronization.Data (in microsoft.synchronization.data.dll)
[SerializableAttribute] [SuppressMessageAttribute("Microsoft.Naming", "CA1706:ShortAcronymsShouldBeUppercase")] public class DbSyncConflict
/** @attribute SerializableAttribute() */ /** @attribute SuppressMessageAttribute("Microsoft.Naming", "CA1706:ShortAcronymsShouldBeUppercase") */ public class DbSyncConflict
In Sync Services, conflicts and errors are detected at the level of the row. A row is in conflict when it has been changed at more than one node between synchronizations. Errors that occur during synchronization typically involve a constraint violation, such as a duplicate primary key. Applications should be designed to avoid conflicts if they can, because conflict detection and resolution introduce additional complexity, processing, and network traffic.
If a row cannot be applied during synchronization, this is usually because either an error or a data conflict occurred. In both cases, the ApplyChangeFailed event is raised. Conflict and error resolution should be handled in response to this event.
For an example of how to handle conflicts, see How to: Handle Data Conflicts and Errors for Peer-to-Peer Synchronization.