Export (0) Print
Expand All
Expand Minimize
This topic has not yet been rated - Rate this topic

PidTagInConflict Canonical Property

Contains TRUE when the attachment represents an alternate replica.

Associated properties:

PR_IN_CONFLICT

Identifier:

0x666C

Data type:

PT_BOOLEAN

Area:

Conflict note

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”:

  1. Last modification time.

  2. Higher CN GUID (using memory compare) to break tie.

Protocol Specifications

[MS-OXPROPS]

Provides references to related Exchange Server protocol specifications.

[MS-OXCSYNC]

Handles synchronizing messaging object data between a server and a client.

Header Files

Mapidefs.h

Provides data type definitions.

Mapitags.h

Contains definitions of properties listed as associated properties.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.