Recurring meeting exception request?

From: Hobietje (Hobietje_at_discussions.microsoft.com)
Date: 10/15/04


Date: Thu, 14 Oct 2004 22:49:06 -0700

Hi Everyone

I am having trouble when I try to change/delete one instance of a recurring
meeting and send a meeting request for this action to the attendees. I got
everything working to update the actual appointment instance, set exdate on
the master, etc. The problem seems to be with the Meeting Request that I
send to the attendees. For some reason Oulook either removes all instances
of the recurring meeting and creates a single meeting for my exception, or
outlook keeps all the recurring meetings (including the one that should be
replaced by my exception) and adds a new single instance meeting for my
exception.

Does anyone know the correct WebDav request to create this meeting request
item that I can send to my attendees? (for both edit/delete of an instance?)
Do I need to send an update for the master item with the exception and then
send a request for the exception? Or how do I get this to work properly with
Outlook and OWA?

Thanks

BTW: I have tried this (including some variations) - this creates a new
seperate appointment instead of an exception:

sqldav = "<?xml version=\"1.0\"?>"
+ "<g:propertyupdate xmlns:e=\"http://schemas.microsoft.com/exchange/\" "
+ "xmlns:g=\"DAV:\" xmlns:c=\"urn:schemas:calendar:\" xmlns:x=\"xml:\" "
+ "xmlns:m=\"urn:schemas:httpmail:\" "
+ "xmlns:header=\"urn:schemas:mailheader:\" "
+ "xmlns:mapi=\"http://schemas.microsoft.com/mapi/\" "
+ "xmlns:dt=\"urn:uuid:c2f41010-65b3-11d1-a29f-00aa00c14882/\" >"
+ "<g:set><g:prop>"
+ "<g:contentclass>urn:content-classes:calendarmessage</g:contentclass>"
+
"<header:contentclass>urn:content-classes:calendarmessage</header:contentclass>"
+
"<e:outlookmessageclass>IPM.Schedule.Meeting.Request</e:outlookmessageclass>"
+ "<m:subject>" + appointment.subject + "</m:subject>"
+ "<m:htmldescription>" + appointment.description + "</m:htmldescription>"
+ "<c:method>REQUEST</c:method>"
+ "<header:to>" + to + "</header:to>"
+ "</g:prop></g:set>"
+ "</g:propertyupdate>";

and I have tried this - this seems to kill all the recurrances and creates a
single item instead:

sqldav = "<?xml version=\"1.0\"?>"
+ "<g:propertyupdate xmlns:e=\"http://schemas.microsoft.com/exchange/\" "
+ "xmlns:g=\"DAV:\" xmlns:c=\"urn:schemas:calendar:\" xmlns:x=\"xml:\" "
+ "xmlns:m=\"urn:schemas:httpmail:\" "
+ "xmlns:header=\"urn:schemas:mailheader:\" "
+ "xmlns:mapi=\"http://schemas.microsoft.com/mapi/\" "
+ "xmlns:dt=\"urn:uuid:c2f41010-65b3-11d1-a29f-00aa00c14882/\" >"
+ "<g:set><g:prop>"
+ "<g:contentclass>urn:content-classes:calendarmessage</g:contentclass>"
+
"<header:contentclass>urn:content-classes:calendarmessage</header:contentclass>"
+
"<e:outlookmessageclass>IPM.Schedule.Meeting.Request</e:outlookmessageclass>"
+ "<m:subject>" + appointment.subject + "</m:subject>"
+ "<m:htmldescription>" + appointment.description + "</m:htmldescription>"
+ "<c:dtstart dt:dt=\"dateTime.tz\">" +
EXConvert.DateTimeToDTString(appointment.StartDate) + "</c:dtstart>"
+ "<c:dtend dt:dt=\"dateTime.tz\">" +
EXConvert.DateTimeToDTString(appointment.EndDate) + "</c:dtend>"
+ "<c:meetingstatus>CONFIRMED</c:meetingstatus>"
+ "<c:busystatus>BUSY</c:busystatus>"
+ "<c:alldayevent>0</c:alldayevent>"
+ "<c:responserequested>1</c:responserequested>"
+ "<c:method>REQUEST</c:method>"
+ "<c:instancetype dt:dt=\"int\">" + appointment.instancetype +
"</c:instancetype>"
+ "<c:timezoneid>76</c:timezoneid>"
+ "<c:rrule><x:v>" + appointment.rrule + "</x:v></c:rrule>"
+ "<c:organizer>" + appointment.Organizer.email + "</c:organizer>"
+ "<mapi:finvited dt:dt=\"boolean\">1</mapi:finvited>"
+ "<mapi:responsestatus dt:dt=\"int\">1</mapi:responsestatus>"
+ "<mapi:responsestate dt:dt=\"int\">0</mapi:responsestate>"
+ "<mapi:response_requested dt:dt=\"boolean\">1</mapi:response_requested>"
+ "<mapi:apptstateflag dt:dt=\"int\">3</mapi:apptstateflag>"
+ "<mapi:busystatus dt:dt=\"int\">1</mapi:busystatus>"
+ "<mapi:intendedbusystatus dt:dt=\"int\">2</mapi:intendedbusystatus>"
+ "<c:uid>" + appointment.uid + "</c:uid>"
+ "<header:to>" + to + "</header:to>"
+ "<c:location>" + loc + "</c:location>";
+ "</g:prop></g:set>"
+ "</g:propertyupdate>";



Relevant Pages

  • Re: How are recurrences stored if we create an exception?
    ... start and end dates of the corresponding exception. ... to the parent recurrence appointment. ... i need to send out a update meeting request to all the ... My problem is sending out the meeting request. ...
    (microsoft.public.win32.programmer.messaging)
  • Re: meeting invitation
    ... Yes same server and same version. ... After that all works fine only meeting request. ... Can You test if there is color at your meeting request at your recipients? ... I also testet it with Outlook 2007. ...
    (microsoft.public.outlook.calendaring)
  • Recurring meeting exceptions
    ... When I make an exception to a meeting, what is the proper XML/WebDav syntax ... I am having issues when I change a single instance of a recurring booking ... Currently I am sending a meeting request as I would for new meetings, ...
    (microsoft.public.exchange2000.development)
  • Re: How to: Create recurring meeting (WebDav)
    ... When I make an exception to a meeting, what is the proper XML/WebDav syntax ... Currently I am sending a meeting request as I would for new meetings, ...
    (microsoft.public.exchange2000.development)
  • Re: meeting to distribution list except one person
    ... P.S. - I'd be interested to know if you could bcc someone on a meeting ... Russ Valentine [MVP-Outlook] wrote: ... > send the meeting request, but it seems a silly way to do it. ...
    (microsoft.public.outlook)