D
Don Schueler
It seems that Outlook does not support iCalendar correctly. Specifically,
using the UID: parameter to allow updating or deleting of existing ICAL
request. Office generates a HUGE UID string itself but it ignores it on
import. You can even export an existing calendar item in iCalendar format,
update it and import back in and it fails in the same way. Here is a SIMPLE
example of the BUG.
The following iCalendar entry works fine to add an inital calendar item:
BEGIN:vCalendar
VERSION:5.0
BEGIN:vEvent
DTSTART:20060601T130000
DTEND:20060601T130000
SUMMARY:Test ONE
UID:64def112-6ede-4396-906e-6e5748db8c2c
END:vEvent
END:vCalendar
The following entry should UPDATE the item above (Summary is different)
because UID is the same, but it doesn't it just adds itself as another
appointment.
BEGIN:vCalendar
VERSION:5.0
BEGIN:vEvent
DTSTART:20060601T130000
DTEND:20060601T130000
SUMMARY:Test TWO
UID:64def112-6ede-4396-906e-6e5748db8c2c
END:vEvent
END:vCalendar
This is messy!
using the UID: parameter to allow updating or deleting of existing ICAL
request. Office generates a HUGE UID string itself but it ignores it on
import. You can even export an existing calendar item in iCalendar format,
update it and import back in and it fails in the same way. Here is a SIMPLE
example of the BUG.
The following iCalendar entry works fine to add an inital calendar item:
BEGIN:vCalendar
VERSION:5.0
BEGIN:vEvent
DTSTART:20060601T130000
DTEND:20060601T130000
SUMMARY:Test ONE
UID:64def112-6ede-4396-906e-6e5748db8c2c
END:vEvent
END:vCalendar
The following entry should UPDATE the item above (Summary is different)
because UID is the same, but it doesn't it just adds itself as another
appointment.
BEGIN:vCalendar
VERSION:5.0
BEGIN:vEvent
DTSTART:20060601T130000
DTEND:20060601T130000
SUMMARY:Test TWO
UID:64def112-6ede-4396-906e-6e5748db8c2c
END:vEvent
END:vCalendar
This is messy!