This is a migrated thread and some comments may be shown as answers.

Breaking Change: Recurrence exception delimiter change

0 Answers 179 Views

Scheduler

This is a migrated thread and some comments may be shown as answers.

This question is locked. New answers and comments are not allowed.

Kendo UI asked on 07 Jun 2016, 12:06 PM

From the official 2016 Q2 Release (2016.2.504) the Scheduler will start using comma (previously semicolon) as delimiter for the recurrence exceptions. Also the Scheduler will no longer add trailing delimiter to the recurrence exception.

This change was required as the previous behavior does not conform to the RFC5545 spec:

http://tools.ietf.org/html/rfc5545#page-120

From the official 2016 Q2 Release (2016.2.504) the Scheduler will start using comma (previously semicolon) as delimiter for the recurrence exceptions. Also the Scheduler will no longer add trailing delimiter to the recurrence exception. This change driven by the RFC5545 spec (previous behavior was incorrect):

http://tools.ietf.org/html/rfc5545#page-120

The following changes are required to all events that have "recurrenceException" set:

Remove the trailing semicolon delimiter
Replace all occurrences of semicolon with comma

//Old recurrence exception:

recurrenceException:"20160603T050000Z;20160503T050000Z;"

//New recurrence exception:

recurrenceException:"20160603T050000Z,20160503T050000Z"

Apologies for the caused inconvenience.