|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
PidTagInConflict Canonical Property
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
Contains TRUE when the attachment represents an alternate replica.
The email client and server must generate a conflict resolve message when detecting a conflict against the current version of a message in the replica during synchronization. It is important to understand that it is possible that the current version of the message in the local replica was transmitted during the current synchronization operation. This will happen when the conflict already exists on the server before any of the conflicting messages were downloaded to the local replica. A conflict resolve message must be synchronized as independent replicas with conflicting PCLs. The conflict resolve message itself must not be synchronized between client and server; only the independent replicas should be exchanged. The synchronization partner must then generate a new message that matches the structure of the conflict message. Therefore, it is important that client and server use the same algorithm to detect the “winner” item. The following rules must be applied to detect the “winner”:
Last modification time.
Higher CN GUID (using memory compare) to break tie.