Thank you for writing back.
The idea of the occurrences is to represent a recurrent appointment. This occurrences are recalculated every time the visible range is changed. Meanwhile, the decision to store/load the Visible
property in the database up to the developer. Some developers do not need to store/load this property and this is the reason why its default value is true
. If you need some additional information about appointment exceptions, we will be glad to answer your questions.
Here is the place to explain that our architecture is to recreate occurrences only in the visible time frame of the scheduler. This means that if you navigate to the next date of the active view then the occurrences will be recreateded according to the new time frame. The occurrences are temporary objects and this is the reason why the occurrences collection is read-only. If you want to modify an occurrence, you should create an exception appointment based on it and add this exception to the Exceptions collection of the master appointment.
Feel free to write back in case of further questions.
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items