188.8.131.52.8 Sending a RopSynchronizationImportHierarchyChange ROP Request
When uploading new folders, clients SHOULD update the ICS state that corresponds to the chosen synchronization scope by adding the Folder ID structures ([MS-OXCDATA] section 184.108.40.206) of new folders to the MetaTagIdsetGiven property (section 220.127.116.11.1) upon successful completion of this ROP.
Changes to parent folders MUST be made before changes to child folders. For example, the client cannot send the RopSynchronizationImportHierarchyChange ROP (section 18.104.22.168.4.3) with a subfolder change before informing the server of the existence of the parent folder.
To move a folder to a different subfolder within the same private mailbox, the client MUST pass the PidTagSourceKey property (section 22.214.171.124.5) of a destination parent folder in the PidTagParentSourceKey property (section 126.96.36.199.6) in the HierarchyValues field while passing the value of the PidTagSourceKey property of the folder being moved in the PidTagSourceKey property. Moving folders within a public mailbox is not supported.