Hello,

I have a situation where users are creating a single never ending recurrence on the scheduler then editing the appointment each week to account for small variances in attributes or resources. This is not a problem except that the "exception" string continues to grow with each change. Currently I have the length of the recurrencerule at 2048 bytes and I don't think the correct solution is to keep extending that columns size.

My preferred solution would be to do something like count the number of exceptions created. I think there are some examples demonstrating a way to do this using parsing and something like "parsedrule.Occurrences". If the count is higher than 50 then I would like to create a new appointment which is a copy of the appointment being modified "newappt = e.appointment" then remove all exceptions from the new appointment and set it with a start date one day past the last exception in the old appointment. Then I would like to change the old appointment from a never ending recurrence to have an end date on the date of its last exception.

Does that make sense?

I've pretty much got it worked out except the copy, creation and modification steps. Is there any easier way to do this? If not, can you give me some pointers to proceed with my concept above?

Thanks!

Hello Andrew,

I will need some more time to provide you with a solution for this issue. I will follow up early next week with my findings.

Kind regards,
Plamen Zdravkov
the Telerik team

Hello Andrew,

Please excuse me for delaying your answer.

Here is one way we can "cut" the recurrence appointment and create the new appointment so that the recurrence rule is in the regular size by catching the ReccurenceExceptionCreated. You can also try the following variation and decide which one fits your needs better:

This one does not have the 24 hour shift as in the attached demo.

Hope this will help you. If you have further questions please don't hesitate to ask.

Regards,
Plamen Zdravkov
the Telerik team

Thanks for that example. I took your example and rewrote it as follows. Could you please review it for any major flaws? Yes the length is short for testing. I will expand it before publishing anything. My goal was to have something that would only create a new recurring appointment after the last exception as to not duplicate or overwrite any existing exceptions. I'm only running into one glitch. I think it has something to do with the end of the recurrence rule being the same time as the last appointment. Occasionally when I "reset" occurrences on any single group created by the code below, either the last appointment is deleted or all the appointments are deleted. It's a little confusing, but I'm working on it.

Below is the code for review. Thanks!!!!!

Hi Andrew,

This behaviour sounds like a known bug in the "reset exceptions"  that is already logged for fixing.
 
All the best,
Plamen Zdravkov
the Telerik team