2.2.1.10 ItemOperations
The ItemOperations command acts as a container for the Fetch element (section 2.2.3.67.1), the EmptyFolderContents element (section 2.2.3.58), and the Move element (section 2.2.3.117.1) to provide batched online handling of these operations against the server.
Operations that are contained within the ItemOperations element (section 2.2.3.94) MUST be executed by the server in the specified order. The server MUST report the status per operation to the client. Accordingly, the client correlates these responses to the initial operation and proceeds appropriately.
The ItemOperations command cannot perform operations on items in the recipient information cache.
The fetch operation is intended to be used on Microsoft Windows SharePoint Services technology, for Universal Naming Convention (UNC) access, or for user mailbox access. Document metadata, search results, and mailbox items and attachments can be retrieved.
The EmptyFolderContents operation enables the client to empty a folder of all its items. Clients typically use the EmptyFolderContents operation to clear out all items in the Deleted Items folder if the user runs out of storage quota.
The Move operation moves a conversation to a destination folder.
The ItemOperations namespace is the primary namespace for this section. Elements referenced in this section that are not defined in the ItemOperations namespace use the namespace prefixes defined in section 2.2.4.
The following table lists the elements that are used in ItemOperations command requests and responses.
|
Element name |
Scope |
Reference |
|---|---|---|
|
ItemOperations |
Request and Response |
section 2.2.3.94 |
|
EmptyFolderContents |
Request and Response |
section 2.2.3.58 |
|
airsync:CollectionId |
Request and Response |
section 2.2.3.30.3 |
|
Options |
Request |
section 2.2.3.125.3 |
|
DeleteSubFolders |
Request |
section 2.2.3.44 |
|
Fetch |
Request and Response |
section 2.2.3.67.1 |
|
Store |
Request |
section 2.2.3.178.2 |
|
airsync:ServerId |
Request and Response |
section 2.2.3.166.7 |
|
documentlibrary:LinkId |
Request and Response |
section 2.2.3.50 |
|
search:LongId |
Request |
section 2.2.3.98.1 |
|
airsyncbase:FileReference |
Request |
section 2.2.3.8 |
|
Schema |
Request |
section 2.2.3.158 |
|
Range |
Request and Response |
section 2.2.3.143.2 |
|
UserName |
Request |
section 2.2.3.193.1 |
|
Password |
Request |
section 2.2.3.132.1 |
|
airsync:MIMESupport |
Request |
section 2.2.3.110.1 |
|
Move |
Request and Response |
section 2.2.3.117.1 |
|
ConversationId |
Request and Response |
section 2.2.3.35.1 |
|
DstFldId |
Request |
section 2.2.3.51.1 |
|
MoveAlways |
Request |
section 2.2.3.118 |
|
Status |
Response |
section 2.2.3.177.8 |
|
Response |
Response |
section 2.2.3.153.4 |
|
airsync:Class |
Response |
section 2.2.3.27.3 |
|
Properties |
Response |
section 2.2.3.139.2 |
|
Total |
Response |
section 2.2.3.184.2 |
|
Data |
Response |
section 2.2.3.39.2 |
|
Part |
Response |
section 2.2.3.130 |
|
Version |
Response |
section 2.2.3.197 |
The XML schema for the ItemOperations command request is described in section 6.23. The XML schema for the ItemOperations command response is described in section 6.24.
Protocol Versions
The following table specifies the protocol versions that support this command. The client indicates the protocol version being used by setting either the MS-ASProtocolVersion header, as specified in [MS-ASHTTP] section 2.2.1.1.2.6, or the Protocol version field, as specified in [MS-ASHTTP] section 2.2.1.1.1.1, in the request.
|
Protocol version |
Command support |
|---|---|
|
2.5 |
|
|
12.0 |
Yes |
|
12.1 |
Yes |
|
14.0 |
Yes |
|
14.1 |
Yes |
|
16.0 |
Yes |
|
16.1 |
Yes |
In protocol version 2.5, items are fetched via the Fetch element of the Sync command, as specified in section 2.2.3.67.2.