7 Appendix B: Product Behavior

  • Article

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Microsoft Office Outlook 2003

  • Microsoft Office Outlook 2007

  • Microsoft Outlook 2010

  • Microsoft Outlook 2013

  • Windows SharePoint Services 2.0

  • Windows SharePoint Services 3.0

  • Microsoft SharePoint Foundation 2010

  • Microsoft SharePoint Foundation 2013

  • Microsoft SharePoint Server 2016

  • Microsoft Outlook 2016

  • Microsoft SharePoint Server 2019

  • Microsoft Outlook 2019

  • Microsoft Outlook 2021

  • Microsoft SharePoint Server Subscription Edition

  • Microsoft Outlook 2024 Preview

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 2.2.5.7:  This type is available only in Outlook 2013 and SharePoint Foundation 2013.

<2> Section 3.1.4:  Office Outlook 2007 uses GetListResult.List.ServerSettings.ServerVersion in GetListResponse (see section 3.1.4.5 and [MS-LISTSWS]) to determine whether Windows SharePoint Services 3.0 supports GetListItemChangesSinceToken. A value of "12.0.0.4326" or greater indicates the server supports GetListItemChangesSinceToken.

<3> Section 3.1.4:  Office Outlook 2003 supports only GetListItemChanges and not GetListItemChangesSinceToken.

<4> Section 3.1.4:  Windows SharePoint Services 2.0 does not support GetListItemChangesSinceToken.

<5> Section 3.1.4.2:  Windows SharePoint Services 3.0 uses AddDiscussionBoardItem to apply the same processing rules that incoming e-mail receives, which includes assigning one e-mail to be the root item described in section 3.2.1.3.

<6> Section 3.1.4.5.1.1:  Office Outlook 2003 and Office Outlook 2007 ignore this attribute.

<7> Section 3.1.4.7:  Office Outlook 2003 uses GetListItems because Office Outlook 2003 does not support GetListItemChangesSinceToken.

<8> Section 3.1.4.7:  In Windows SharePoint Services 3.0 and SharePoint Foundation 2010, if there is no "query" element in the request, the server will sort items by the ID field, in ascending order.

<9> Section 3.1.4.7:  Office Outlook 2007 sets rowLimit to 100 by default.rowLimit can be configured to use a number between 15 and 1000. Office Outlook 2007 omits rowLimit when using this protocol to download appointments.

<10> Section 3.1.4.7:  Office Outlook 2003 and Windows SharePoint Services 2.0 do not support the "v3" recurrence patterns listed here.

<11> Section 3.1.4.8:  The Translate header is a Microsoft extension to the HTTP specification used in conjunction with WebDAV functionality.

<12> Section 3.2.1.1.2:  Windows SharePoint Services 2.0, Windows SharePoint Services 3.0, SharePoint Foundation 2010, and SharePoint Foundation 2013 allow this. Office Outlook 2003, Office Outlook 2007, Outlook 2010, and Outlook 2013 do not allow this.

<13> Section 3.2.1.1.3:  Office Outlook 2003 and Office Outlook 2007 treat exception items that have no recurrence as single appointments (section 3.2.1.1.1).

<14> Section 3.2.1.1.3:  Office Outlook 2003 and Office Outlook 2007 do not support restoring instances of a recurrence once they have become exceptions. Windows SharePoint Services 2.0 and Windows SharePoint Services 3.0 allow this.

<15> Section 3.2.1.1.4:  Windows SharePoint Services 2.0 and Windows SharePoint Services 3.0 can be configured to display deleted instance items.

<16> Section 3.2.1.1.4:  Windows SharePoint Services 2.0 and Windows SharePoint Services 3.0 convert exception items to deleted instance items and remove some of the data on the items. Office Outlook 2007 deletes the exception item and uploads a deleted instance item to replace it.

<17> Section 3.2.4.1:  Office Outlook 2003 ignores MinTimeBetweenSyncs. Office Outlook 2007 can be configured to ignore MinTimeBetweenSyncs.

<18> Section 3.2.4.2:  Office Outlook 2003 reads only the following fields, ignores all other appointment-specific fields, and reads these only if they are in the server's current schema:

  • Description

  • Duration

  • EndDate

  • EventDate

  • EventType

  • FooterInfo

  • fRecurrence

  • HeaderInfo

  • LinkTitle

  • Location

  • RecurrenceData

  • RecurrenceID

  • UID

  • XMLTZone

<19> Section 3.2.4.2:  Office Outlook 2003 reads only the following field, ignores all other contact-specific fields, and reads these only if they are in the server's current schema:

  • Birthday

  • CellPhone

  • Comments

  • Company

  • CompanyPhonetic

  • Email

  • FileAs

  • FirstName

  • FirstNamePhonetic

  • HomeAddress

  • HomeCity

  • HomeCountry

  • HomePhone

  • HomeState

  • HomeZip

  • JobTitle

  • LastNamePhonetic

  • MiddleName

  • NameTitle

  • OfficeLocation

  • Suffix

  • Title

  • WebPage

  • Wedding

  • WorkAddress

  • WorkCity

  • WorkCountry

  • WorkFax

  • WorkPhone

  • WorkState

  • WorkZip

<20> Section 3.2.4.2.1:  Office Outlook 2003 reads only the following fields and ignores all other common properties:

  • ID

  • Attachments

<21> Section 3.2.4.2.1:  Office Outlook 2007 will use ReplicationID only if it is a property bag field.

<22> Section 3.2.4.2.1:  Office Outlook 2007 will use vti_versionhistory only if it is a property bag field.

<23> Section 3.2.4.2.1:  Office Outlook 2003 ignores ContentTypeId. Office Outlook 2007 ignores ContentTypeId on calendar lists.

<24> Section 3.2.4.2.1:  Office Outlook 2007 and Windows SharePoint Services 3.0 can remove old GUID-integer pairs if the version history becomes large.

<25> Section 3.2.4.2.2:  Office Outlook 2003 reads only the following fields, ignores all other appointment-specific fields, and reads these only if they are in the server's current schema:

  • Description

  • Duration

  • EndDate

  • EventDate

  • EventType

  • FooterInfo

  • fRecurrence

  • HeaderInfo

  • LinkTitle

  • Location

  • RecurrenceData

  • RecurrenceID

  • UID

  • XMLTZone

<26> Section 3.2.4.2.2:  Windows SharePoint Services 2.0 does not have the fAllDayEvent field.  Office Outlook 2003 ignores the fAllDayEvent field.

<27> Section 3.2.4.2.3:  Windows SharePoint Services 2.0 does not delete exception items when these properties are updated.

<28> Section 3.2.4.2.4:  Office Outlook 2003 reads only the following fields, ignores all other contact-specific fields, and reads these only if they are in the server's current schema:

  • Birthday

  • CellPhone

  • Comments

  • Company

  • CompanyPhonetic

  • Email

  • FileAs

  • FirstName

  • FirstNamePhonetic

  • HomeAddress

  • HomeCity

  • HomeCountry

  • HomePhone

  • HomeState

  • HomeZip

  • JobTitle

  • LastNamePhonetic

  • MiddleName

  • NameTitle

  • OfficeLocation

  • Suffix

  • Title

  • WebPage

  • Wedding

  • WorkAddress

  • WorkCity

  • WorkCountry

  • WorkFax

  • WorkPhone

  • WorkState

  • WorkZip

<29> Section 3.2.4.2.4:  Office Outlook 2003 and Office Outlook 2007 use Wedding instead of Anniversary for this field.

<30> Section 3.2.4.2.4:  Office Outlook 2007 interprets this field as an integer Gender only. Clients SHOULD interpret it as a choice type when the server includes CHOICE and MAPPING elements.

<31> Section 3.2.4.2.4:  Office Outlook 2003 and Office Outlook 2007 use HomeCity instead of HomeAddressCity for this field.

<32> Section 3.2.4.2.4:  Office Outlook 2003 and Office Outlook 2007 use HomeCountry instead of HomeAddressCountry for this field.

<33> Section 3.2.4.2.4:  Office Outlook 2003 and Office Outlook 2007 use HomeZip instead of HomeAddressPostalCode for this field.

<34> Section 3.2.4.2.4:  Office Outlook 2003 and Office Outlook 2007 use HomeState instead of HomeAddressStateOrProvince for this field.

<35> Section 3.2.4.2.4:  Office Outlook 2003 and Office Outlook 2007 use OfficeLocation instead of Office for this field.

<36> Section 3.2.4.2.4:  Microsoft Office SharePoint Server 2007 and Microsoft SharePoint Server 2010 do not include the MAPPINGS element for the Gender field.

<37> Section 3.2.4.2.8:  For Windows SharePoint Services 3.0 and SharePoint Foundation 2010, the default type is User, for SharePoint Foundation 2013, the default type is UserMulti.

<38> Section 3.2.4.2.8:  Office Outlook 2007 serves as a pass-through for this data.