2.2.2.37 Recurrence

  • Article

The Recurrence element is an optional container ([MS-ASDTYPE] section 2.2) element that specifies the recurrence pattern for the calendar item. It is defined as an element in the Calendar namespace and is used in ActiveSync command requests and responses as specified in section 2.2.2.

The Recurrence element can have the following child elements:

  • Type (section 2.2.2.45): One instance of this element is required in protocol versions 2.5, 12.0, 12.1, 14.0, and 14.1; optional in protocol versions 16.0 and 16.1.

  • Occurrences (section 2.2.2.32): This element is optional.

  • Interval (section 2.2.2.25): This element is optional.

  • WeekOfMonth (section 2.2.2.48): This element is optional.

  • DayOfWeek (section 2.2.2.15): This element is optional.

  • MonthOfYear (section 2.2.2.29): This element is optional.

  • Until (section 2.2.2.47): This element is optional.

  • DayOfMonth (section 2.2.2.14): This element is optional.

  • CalendarType (section 2.2.2.10): This element is optional in daily and yearly recurrences.

  • IsLeapMonth (section 2.2.2.26): This element is optional.

  • FirstDayOfWeek (section 2.2.2.24): This element is optional.

The following limitations apply to the Recurrence element:

  • The Recurrence element MUST NOT specify multiple occurrences that begin on the same day.

  • The Recurrence element MUST NOT specify occurrences that overlap with each other or with any exceptions. An exception that modifies the start date of an instance in the recurring series MUST occur on a date that is sometime after the end of the prior instance and before the start of the next instance in the recurring series. The same is true if the prior or next instance in the recurring series is defined as an exception by using the Exceptions element.

For more details about recurrence patterns, see [MS-OXOCAL] section 2.2.1.44.

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

In protocol version 16.0 and 16.1: Changing the recurrence pattern of a recurring series will delete any exceptions present on the calendar item; the Type element is optional in client requests; the client can change a recurring event to a single event by including an empty Recurrence element in its request.