Problem with updating recurranceexception.

[Pär Sandgren]

Hello,

When updating an item in a series, the scheduler first calls Create, with the new item, then Update to add the recurrenceexception. In my case, I have some servervalidation to check if recurrences are overlapping, and that check fails since the old post hasn't been updated.

Is there any way to control this order? Is it stupid to do it in the source?

Regards,
Pär Sandgren

[Georgi Krustev]

Hello Par,

The SchedulerDataSource is designed to first create the exception event and then to add the recurrence exception date in the recurrence head. That is why the first request is create and the next one is update. This order cannot be controlled. Did you have a chance to check Restriction demo of the scheduler? It shows how to prevent event overlapping. Is it suitable for your business case?

Regards,
Georgi Krustev
Telerik

[Pär Sandgren]

Hi Georgi,

The problem with the restriction demo is that it only restricts single events. I need to restrict recurrences from overlapping. Since we already force the user to set an end for the recurrence (either by date or number), it shouldn't cause any problems. I couldn't get the extend-method working to loop through things, so I made a server-side check, but that fails since the create comes first. 

// Pär

[Georgi Krustev]

Hello again Pär,

As I pointed in my previous reply, the order of the requests cannot be controlled and it will not change in future. The occurrencesInRange method will return all events + occurrences in recurring series, and thus the validation will be correct as it will check not only the single events. Could you share why this logic is not suitable for you?

Regards,
Georgi Krustev
Telerik