Hi All,
Can someone tell me what is the correct way to handle deletes programmatically for occurrences and recurrence exceptions?
Deleting a simple, non-recurring booking with a call to RadScheduleView.Remove(apptA) causes the RadScheduleView.AppointmentDeleted event to fire.. From this event, we can remove apptA from our data store--finalising the "delete" operation. The same path is taken when deleting a recurring series. Removing the series "Master" from the RadScheduleView and then the data store removes all occurrences.
But what about deleting only one occurrence out of several or deleting an exception to the recurrence rule? This does not cause AppointmentDeleted to fire, so how do we finalise the "delete" operation? What happens behind the scenese? What entities are affected?
Also, according to this page, "you can delete an appointment using the code. Just Call Remove() method of the RadScheduleView control. It returns whether or not the appointment or the occurrence can be removed." Why might an appointment NOT be removable? Also note that we are managing our AppointmentSource, loading and unloading appointments as users move forward and back in time. We are not able to use the CollectionChanged handler of this collection to watch for deletions or additions.
Thanks for your help--
Scott
Can someone tell me what is the correct way to handle deletes programmatically for occurrences and recurrence exceptions?
Deleting a simple, non-recurring booking with a call to RadScheduleView.Remove(apptA) causes the RadScheduleView.AppointmentDeleted event to fire.. From this event, we can remove apptA from our data store--finalising the "delete" operation. The same path is taken when deleting a recurring series. Removing the series "Master" from the RadScheduleView and then the data store removes all occurrences.
But what about deleting only one occurrence out of several or deleting an exception to the recurrence rule? This does not cause AppointmentDeleted to fire, so how do we finalise the "delete" operation? What happens behind the scenese? What entities are affected?
Also, according to this page, "you can delete an appointment using the code. Just Call Remove() method of the RadScheduleView control. It returns whether or not the appointment or the occurrence can be removed." Why might an appointment NOT be removable? Also note that we are managing our AppointmentSource, loading and unloading appointments as users move forward and back in time. We are not able to use the CollectionChanged handler of this collection to watch for deletions or additions.
Thanks for your help--
Scott