I would suggest that you save the exceptions in a separate tables as in our Database example, you can check the used in the example schema in this help topic
. Note that the exceptions can be of two types:
- when an occurrence of a recurrent appointment is deleted -in this case you could save only the exception date.
- when an occurrence of a recurrent appointment is edited - you should save all the properties of the exception separately, that is why we have in the example SqlExceptionAppointments, SqlExceptionResources tables.
When an occurrence is edited/deleted, the AppointmentEditing/Edited events of the parent appointment are fired, so you could use them to update the database. More information on the ScheduleView events can be found here.
I hope this helps.