I'm running into a problem where resetting exceptions on a repeating appointment causes the first appointment to disappear from the Scheduler. Using the demo project from this page in the knowledge base, the following steps will reproduce the issue.
1. Open project in VS2010
2. Run project conversion wizard
3. Convert project to .Net 4.0
4. Remove reference to old version of Telerik.Web.UI
5. Add reference to installed trial version (2010.2.713.40) of Telerik.Web.UI for .Net 4.0
6. Run project
7. Switch Scheduler to week view
8. Create and save test appointment on 8/17/2010, 9:00am-10:00am, repeats weekly on Tuesdays, no end date
9. In Scheduler, drag appointment on 8/17/2010 to a different timeslot, creating exception
10. Double click on appointment on 8/17/2010, and edit series
11. Click and confirm 'reset exceptions'
12. Click 'Save' in open appointment editor
At this point, the appointment on 8/17/2010 no longer shows up, though subsequent repeating occurrences are shown correctly. By checking the xml data file at various steps, it appears that the appointment is being save correctly after step 11, but after step 12, the recurrence rule incorrectly shows an exception date.
after step 8
after step 9
after step 11
after step 12
Is there a way to prevent this behavior? I've tried a few things with some of the client side events, but haven't had much luck yet.
Thanks
1. Open project in VS2010
2. Run project conversion wizard
3. Convert project to .Net 4.0
4. Remove reference to old version of Telerik.Web.UI
5. Add reference to installed trial version (2010.2.713.40) of Telerik.Web.UI for .Net 4.0
6. Run project
7. Switch Scheduler to week view
8. Create and save test appointment on 8/17/2010, 9:00am-10:00am, repeats weekly on Tuesdays, no end date
9. In Scheduler, drag appointment on 8/17/2010 to a different timeslot, creating exception
10. Double click on appointment on 8/17/2010, and edit series
11. Click and confirm 'reset exceptions'
12. Click 'Save' in open appointment editor
At this point, the appointment on 8/17/2010 no longer shows up, though subsequent repeating occurrences are shown correctly. By checking the xml data file at various steps, it appears that the appointment is being save correctly after step 11, but after step 12, the recurrence rule incorrectly shows an exception date.
after step 8
<
Appointment
>
<
ID
>49</
ID
>
<
Subject
>test</
Subject
>
<
Start
>2010-08-17T09:00Z</
Start
>
<
End
>2010-08-17T10:00Z</
End
>
<
RecurrenceRule
>
<![CDATA[DTSTART:20100817T090000Z
DTEND:20100817T100000Z
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=TU;WKST=
]]>
</
RecurrenceRule
>
</
Appointment
>
after step 9
<
Appointment
>
<
ID
>49</
ID
>
<
Subject
>test</
Subject
>
<
Start
>2010-08-17T09:00Z</
Start
>
<
End
>2010-08-17T10:00Z</
End
>
<
RecurrenceRule
>
<![CDATA[DTSTART:20100817T090000Z
DTEND:20100817T100000Z
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=TU
EXDATE:20100817T090000Z
]]>
</
RecurrenceRule
>
</
Appointment
>
<
Appointment
>
<
ID
>50</
ID
>
<
Subject
>test</
Subject
>
<
Start
>2010-08-17T10:00Z</
Start
>
<
End
>2010-08-17T11:00Z</
End
>
<
RecurrenceParentID
>49</
RecurrenceParentID
>
</
Appointment
>
after step 11
<
Appointment
>
<
ID
>49</
ID
>
<
Subject
>test</
Subject
>
<
Start
>2010-08-17T09:00Z</
Start
>
<
End
>2010-08-17T10:00Z</
End
>
<
RecurrenceRule
>
<![CDATA[DTSTART:20100817T090000Z
DTEND:20100817T100000Z
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=TU
]]>
</
RecurrenceRule
>
</
Appointment
>
after step 12
<
Appointment
>
<
ID
>49</
ID
>
<
Subject
>test</
Subject
>
<
Start
>2010-08-17T09:00Z</
Start
>
<
End
>2010-08-17T10:00Z</
End
>
<
RecurrenceRule
>
<![CDATA[DTSTART:20100817T090000Z
DTEND:20100817T100000Z
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=TU
EXDATE:20100817T090000Z
]]>
</
RecurrenceRule
>
</
Appointment
>
Is there a way to prevent this behavior? I've tried a few things with some of the client side events, but haven't had much luck yet.
Thanks