Assembly: Microsoft.Synchronization.Data (in microsoft.synchronization.data.dll)
|Continue||Continue processing, and add the row to the list of conflicts that are defined in the SyncConflict object. This is the default behavior.|
|RetryApplyingRow||Try to apply the row one more time.|
|RetryNextSync||Store the row as an exception, and try to apply the row during the next synchronization session. Only valid for peer to peer synchronization.|
|RetryWithForceWrite||Force the row to be applied by using logic that is included in synchronization adapter commands.|
If a row cannot be applied during synchronization, the ApplyChangeFailed event is raised. The ApplyChangeFailedEventArgs object provides information about the error or conflict that caused the failure. In a handler for the event, you can specify whether the synchronization provider should try to apply the row again. Force writing changes on the client is handled by the client synchronization provider. Force writing changes on the server requires logic in the code that applies changes to the server. For more information, see How to: Handle Data Conflicts and Errors.
The following code example specifies a value of
RetryWithForceWrite for client-update/server-delete conflicts. To view this code in the context of a complete example, see How to: Handle Data Conflicts and Errors.