Share via

3.2.5.9.4.3 Receiving a RopSynchronizationImportHierarchyChange ROP Request

  • Article

When the client sends the server a RopSynchronizationImportHierarchyChange ROP (section 2.2.3.2.4.3) request, the server MUST parse the request, as specified in [MS-OXCROPS] section 2.2.13.4.1 and section 2.2.3.2.4.3 of this specification. The server MUST respond with a RopSynchronizationImportHierarchyChange ROP response, as specified in [MS-OXCROPS] section 2.2.13.4.2 or 2.2.13.4.3, and section 2.2.3.2.4.3 of this specification.

Upon successful completion of this ROP, the ICS state on the synchronization context MUST be updated to include a new change number in the MetaTagCnsetSeen property (section 2.2.1.1.2).

The server is responsible for conflict detection and resolution, as specified in section 3.1.5.6.

If a conflict is detected, the server MUST resolve it as specified in section 3.1.5.6.2 and return Success. A server can report a conflict using a conflict notification message.

If a conflict has occurred, the server:

  • SHOULD NOT update the MetaTagCnsetSeen property, and let the clients download a result of conflict resolution.

  • MAY generate a conflict notification message. For more details, see section 3.1.5.6.3.

  • MUST return a value of Success in the ReturnValue field.

The server MUST ignore the properties in the PropertyValues field, which are also present in the HierarchyValues field.