|
|
The KB article that describes the chnages in 2003 SP2, also mentions the
real appointment id, which does stay the same:
http://support.microsoft.com/kb/899919
Use the following property instead:
schemas.microsoft.com/mapi/id/{6ED8DA90-450B-101B-98DA-00AA003F1305}/00030102">http://schemas.microsoft.com/mapi/id/{6ED8DA90-450B-101B-98DA-00AA003F1305}/00030102
Dmitry Streblechenko (MVP)
www.dimastr.com/">http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool
"tormork" <tormork@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AD35B513-1D00-4F18-BDB5-0586FC8CD344@xxxxxxxxxxxxxxxx
>I do not get the idea behind ids an appointments.
>
> I have a synchronous create and delete event which I use for synchronizing
> Exchange Calendendars to another system.
>
> In Exchange 2000 and Exchange 2003 it has been quite simple to use
> urn:schemas:calendar:uid as a unique identifier.
>
> However Outlook 2003 sp 2 ended this. When a meeting invitation i accepted
> in outl. 2003 sp2 a new copy of the appointment is made, with the same
> urn:schemas:calendar:uid as the original, then the original is deleted.
> There
> are now to appointments with the same id and only one of them is deleted.
>
> Obviously a synchronization that runs in an synchornous Event sink will
> fail
> here becase it is reported "wrongly" that an appointment is deleted. This
> was
> somewhat difficult to get around and required overhead, which I was not
> willing to use, so I started using the
> schemas.microsoft.com/exchange/permanenturl">http://schemas.microsoft.com/exchange/permanenturl which obviously(and
> according to documentation) should be unique. This seem to work ok, but
> now
> it seems that the schemas.microsoft.com/exchange/permanenturl">http://schemas.microsoft.com/exchange/permanenturl of
> recurring appointments changes before the delete event sink is called and
> hence my synchronization does not detect the appointment as a synchronized
> one.
>
> The only possible way seem to use on set of logic for WebOutlook and a
> seperate one for Outlook 2003 sp2+, but it does not seem to be a logical
> thing to do. Also it seem complicated at best(if possible).
>
> So does anyone have some idea of how an Outlook appointment can be uniquly
> identified in an event sink?
|
|