2.2.3.11 ApplicationData

The ApplicationData element is a required child element of the Change element and the Add element in Sync command requests, and a required child element of the Change element, the Add element, and the Fetch element in Sync command responses. It contains data for a particular object, such as a contact, email message, calendar appointment, or task item. The ApplicationData element can be used to change items, add items, or fetch items on the client device or server. The format of this data is determined by the schema for the object.

Elements referenced in this section are defined in the AirSync 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

Sync command request (section 2.2.1.21)

Change (section 2.2.3.24)

Add (section 2.2.3.7.2)

Data elements from the content classes. For details about the content classes, see [MS-ASCAL], [MS-ASCNTC], [MS-ASEMAIL], [MS-ASMS], [MS-ASNOTE], and [MS-ASTASK].

airsyncbase:Location ([MS-ASAIRS] section 2.2.2.28)

container ([MS-ASDTYPE] section 2.2)

1…1 (required)

Sync command response

Change (section 2.2.3.24)

Add (section 2.2.3.7.2)

Data elements from the content classes. For details about the content classes, see [MS-ASCAL], [MS-ASCNTC], [MS-ASDOC], [MS-ASEMAIL], [MS-ASMS], [MS-ASNOTE], and [MS-ASTASK].

airsyncbase:Body ([MS-ASAIRS] section 2.2.2.9)

airsyncbase:BodyPart ([MS-ASAIRS] section 2.2.2.10)

airsyncbase:NativeBodyType ([MS-ASAIRS] section 2.2.2.32)

rm:RightsManagementLicense ([MS-ASRM] section 2.2.2.14)

airsyncbase:InstanceId ([MS-ASAIRS] section 2.2.2.25)

airsyncbase:Location

container

1…1 (required)

Sync command response

Fetch (section 2.2.3.67.2)

airsyncbase:Attachments ([MS-ASAIRS] section 2.2.2.8)

airsyncbase:Body

airsyncbase:NativeBodyType

airsyncbase:Location

rm:RightsManagementLicense

Data elements from the content classes. For details about the content classes, see [MS-ASCAL], [MS-ASCNTC], [MS-ASDOC], [MS-ASEMAIL], [MS-ASMS], and [MS-ASTASK].

container

1…1 (required)

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

Yes

12.0

Yes

12.1

Yes

14.0

Yes

14.1

Yes

16.0

Yes

16.1

Yes