Hi,
We have come across an issue with Hourly Event. To explain it further, I'm going to provide the step-by-step procedure on how to recreate it... please see below:
(1) From the Calendar, double click on one of the time slots.
(2) Create an Event with the following information:
--> From 8/7/2008 12:00AM To 8/7/2008 1:00AM
--> Check the "Recurring appointment" box
--> Under the Recurrence, select "Hourly" and then set it to "Every 2
hours"
--> Under the Range of Recurrence, select "End by this date:" with the
date set to 8/7/2008.
(3) Once the event is created, you will notice that there are hourly events for 8/7/2008 (which is correct, by the way)... and then a single hourly event (from 12AM to 1AM) under 8/8/2008.
I looked at the database and here is the RecurrencePattern field value:
Thanks so much for your time and appreciate your help.
We have come across an issue with Hourly Event. To explain it further, I'm going to provide the step-by-step procedure on how to recreate it... please see below:
(1) From the Calendar, double click on one of the time slots.
(2) Create an Event with the following information:
--> From 8/7/2008 12:00AM To 8/7/2008 1:00AM
--> Check the "Recurring appointment" box
--> Under the Recurrence, select "Hourly" and then set it to "Every 2
hours"
--> Under the Range of Recurrence, select "End by this date:" with the
date set to 8/7/2008.
(3) Once the event is created, you will notice that there are hourly events for 8/7/2008 (which is correct, by the way)... and then a single hourly event (from 12AM to 1AM) under 8/8/2008.
I looked at the database and here is the RecurrencePattern field value:
DTSTART:20080809T000000Z DTEND:20080809T010000Z RRULE:FREQ=HOURLY;UNTIL=20080810T000000Z;INTERVAL=2
Is this a valid test? Is this a bug? What behavior of RadScheduler do we expect given the test details?Thanks so much for your time and appreciate your help.
1 Answer, 1 is accepted
0
Hi Annie,
Actually, this is the expected behavior. The "Repeat until" date is inclusive and that is why you are getting one "extra" occurrence.
We try to follow the RFC-2445 specification as close as possible when dealing with recurring appointments. Here is what it says about the UNTIL element:
"The UNTIL rule part defines a date-time value which bounds the
recurrence rule in an inclusive manner. If the value specified by
UNTIL is synchronized with the specified recurrence, this date or
date-time becomes the last instance of the recurrence."
I hope this helps.
All the best,
Tsvetomir Tsonev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Actually, this is the expected behavior. The "Repeat until" date is inclusive and that is why you are getting one "extra" occurrence.
We try to follow the RFC-2445 specification as close as possible when dealing with recurring appointments. Here is what it says about the UNTIL element:
"The UNTIL rule part defines a date-time value which bounds the
recurrence rule in an inclusive manner. If the value specified by
UNTIL is synchronized with the specified recurrence, this date or
date-time becomes the last instance of the recurrence."
I hope this helps.
All the best,
Tsvetomir Tsonev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.