The desired result can be achieved, but the implementation should happen on the server. The Scheduler is working with the RFC5545 standard and is creating the recurrence rules according to it. You could use an RFC5545 parser and implement a custom logic that will parse the recurrence rule to different events data based on the initial event. Once you have information on all the events you could store the EndDate of the last one.
For example, if a recurring daily event is created, for three occurrences only the RecurrenceRule would look something like this:
"Title": "No title",
What you would need to do to get the EndDate of the particular recurring event
- Subscribe to the save event to get the data on the newly created or edited event.
- Send the event data to the server
- If a recurrence rule is present parse it using an RFC5545 parser and get a list of all events. If no rule is present then this is a single-time event. As you noticed if an EndDate of the recurrence is specified it is present in the RecurrenceRule.
- Once you have all events you can get the EndDate of the last event.
I hope this guide helps you implement the desired functionality. Let me know if you have further questions.
Get quickly onboarded and successful
with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.