When repeating meetings are created, only one child document is created to the main calendar entry which stores the repeat info. If one or more of the repeats is changed, notes breaks this child document up and creates siblings. Is there any way to automate this so that when a repeating appointment is created in the first place, all the repeating dates are broken up into separate child documents?
I know the response is late but I’ve been working on a split function that will do that on a need to do basis. If anyone is still interested I can post the code (it’s in C++ using COM).
I am creating a system which will show agenda items against a particular calendar entry. It works fine for single entries because I can use the ApptUNID as a reference. If, however the appointment repeats, I can think of now way in which to associate my agenda documents to the individual repeat instance, without first separating them from their shared child document.