2.2.3.8 airsyncbase:FileReference
The airsyncbase:FileReference element is an optional child element of the Fetch element in ItemOperations command requests and responses that specifies a unique identifier that is assigned by the server to each attachment to a given item.
Elements referenced in this section are defined in the ItemOperations namespace, except where otherwise indicated by the presence of a namespace prefix (as defined in section 2.2.4).
|
Command request/response |
Parent elements |
Child elements |
Data type |
Number allowed |
|---|---|---|---|---|
|
ItemOperations command request and response (section 2.2.1.10) fetch operation |
Fetch (section 2.2.3.67.1) |
None |
string ([MS-ASDTYPE] section 2.7) |
0...1 (optional) |
The client MUST store the file reference for any item that is retrieved by means of the Sync command (section 2.2.1.21) or Search command (section 2.2.1.16). In an ItemOperations request, only one airsyncbase:FileReference identifier can exist per Fetch node. Violation of this constraint results in a Status element (section 2.2.3.177.8) value of 2 being returned from the server. The client can, however, retrieve multiple attachments by using one Fetch node per attachment.
If the airsyncbase:FileReference element is present, then the Range element (section 2.2.3.143.2) is the only valid child element of the Options element (section 2.2.3.125.3).
Protocol Versions
The following table specifies the protocol versions that support this element. 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 |
Element support |
|---|---|
|
2.5 |
|
|
12.0 |
Yes |
|
12.1 |
Yes |
|
14.0 |
Yes |
|
14.1 |
Yes |
|
16.0 |
Yes |
|
16.1 |
Yes |