In general, the nature of the recurring series is treated as one appointment, rather than a collection of appointments. That being said, in the database should be saved a single record for the master appointment. The recurrence rule which describes the repetition pattern of the event should be preserved in a separate property which the Scheduler expects to receive on the client side as 'recurrenceRule'.
The occurences of the master appointment are generated automatically on the client by the Scheduler and depend entirely on their master event. The occurences do not have their own Id set and are associated to the master event through the recurrenceId field.
From the provided screenshot I can see that the recurrenceRule is not being set when the event is saved. Thus, when refreshing the Scheduler this leads to the observed behavior where the event is not being associated correctly.
I would suggest referring to the following Ajax Binding Documentation for ASP.NET MVC
that provides a detailed list of steps on how to set up the Scheduler. The recommended approach is to use the linked example as a starting point and then decorate it further with the desired options and functionality.
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.