When I create a recurring daily appointment series that lasts for multiple days, it does not show up for all those multiple days. It almost seems like RadScheduler stops displaying the series of appointments past the week that it was created in. The RecurrenceRule text in the database however contains the correct and intended information. The same thing happens if I create a recurring appointment that ends on a specific date. It somehow shows for only the week it was created in event though the RecurrenceRule text in the database contains the end date that was assigned to the series. For example:
DTSTART:20100927T120000Z DTEND:20100927T130000Z RRULE:FREQ=DAILY;COUNT=15;INTERVAL=1;BYDAY=MO,TU,WE,TH,FR,SA,SU2 Answers, 1 is accepted
0
Alankar
Top achievements
Rank 1
Rank 1
answered on 29 Sep 2010, 07:04 PM
I noticed one more interesting thing...I thought I would create a new recurring appointment through a monthly view to see if this issue has something to do with the current visible range. Once I created one, it appeared for all 15 days in the month that I scheduled for. Not only that, the appointment referenced to in the first post of this thread started showing up for all days it was supposed to. However, when I refreshed the browser page, the RadScheduler switched to weekly view by default, consequently not displaying any of these 2 recurring appointments that I talked about beyond the current week. I have a feeling that the current visible range and/or selected view may have something to do with this.
0
Hello Alankar,
Can you please provide more details on your implementation? Ideally, you should open a support ticket and send us a simple demo of the issue.
In general, the recurrence master is stored in the database and its occurrences are generated on the fly using the recurrence rule of the appointment. For more information, please see the help topic on Working with Recurring Appointments.
Greetings,
Peter
the Telerik team
Can you please provide more details on your implementation? Ideally, you should open a support ticket and send us a simple demo of the issue.
In general, the recurrence master is stored in the database and its occurrences are generated on the fly using the recurrence rule of the appointment. For more information, please see the help topic on Working with Recurring Appointments.
Greetings,
Peter
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items