I just had a look at the soap.txt file in the SVN. The SVN is out of date.
Here are the latest SOAP docs. Also, we have a 4.5.8 source tar with the latest SOAP docs.
Here they are:
I noticed in the soap.txt there was more about the comp tag & exceptions:
let me know if this doesn't help.
// CREATING EXCEPTIONS
// Just like CreateAppointment, except that instead of specifying a target FOLDER, you
// specify an existing PID and component-number
// *** If id= and comp= are set, then you are creating an EXCEPTION:
// The default invite for the appointment MUST have a recurrence rule....
// otherwise you should just be using ModifyAppointment!
// EXCEPTION_ID is start-time for the particular instance you are overriding
// EXCEPTION_ID MUST be some instance that matches the default-invite for
// the appointment...that is, it MUST NOT BE the start time of the exception!
// **The above is important** So let me explain:
// Given an appointment, happens every Wednesday @ 9am, with an exception that moves
// it to 10am on 6/22
// So our instances for June, 2005 are:
// 6/1 9am
// 6/8 9am
// 6/15 9am
// 6/22 10am (an existing EXCEPTION)
// 6/29 9am
// So, if a user clicks on the 6/22 10am appointment and wants to modify it, you MUST NOT
// try to use <CreateAppointmentExceptionRequest> to modify it!
// You MUST use ModifyAppointmentRequest instead!!!
// On the other hand, if a user clicks on the 6/15 9am appointment and wants to modify it,
// then this is the right API to use.