2 Apr
2014
2 Apr
'14
7:33 a.m.
I presume both VEVENTS are enclosed in the same VCALENDAR object, are they?
That's correct behavior. In this case both events *must* have the same
UID because it's essentially the same event (just with an exception).
The exception instance has a RECURRENCE-ID to specify the exact instance
of the event that is replaced by the exception.
cheers
Marten
Am 02.04.2014 08:39, schrieb Johan Vromans:
Hi,
I use Business Calendar Pro on Android. I change one occurrence of a
repeating appointment to a different time and now I have a duplicate ID
on the DAViCal server:
BEGIN:VEVENT
CREATED:20140106T230106Z
SUMMARY:****
TRANSP:OPAQUE
CLASS:PUBLIC
DTSTART;TZID=Europe/Berlin:20140226T093000
LOCATION:****
STATUS:CONFIRMED
EXDATE:20140312T083000Z
EXDATE:20140326T083000Z
EXDATE:20140319T083000Z
RRULE:FREQ=WEEKLY;WKST=MO;UNTIL=20141224T083000Z
DURATION:PT2H30M
LAST-MODIFIED:20140320T214312Z
DTSTAMP:20140320T214312Z
SEQUENCE:3
UID:bkdiwaiy-cmbs-xjpc-pe24-gd16ybt4mfeu
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=Europe/Berlin:20140402T103000
SUMMARY:****
LOCATION:****
CLASS:PUBLIC
TRANSP:OPAQUE
STATUS:CONFIRMED
DTEND;TZID=Europe/Berlin:20140402T123000
LAST-MODIFIED:20140401T221005Z
DTSTAMP:20140401T221005Z
SEQUENCE:1
RECURRENCE-ID:20140402T073000Z
UID:bkdiwaiy-cmbs-xjpc-pe24-gd16ybt4mfeu
END:VEVENT
This was the original event:
BEGIN:VEVENT
CREATED:20140106T230106Z
SUMMARY:****
TRANSP:OPAQUE
CLASS:PUBLIC
DTSTART;TZID=Europe/Berlin:20140226T093000
LOCATION:****
STATUS:CONFIRMED
EXDATE:20140312T083000Z
EXDATE:20140326T083000Z
EXDATE:20140319T083000Z
RRULE:FREQ=WEEKLY;WKST=MO;UNTIL=20141224T083000Z
DURATION:PT2H30M
LAST-MODIFIED:20140320T214312Z
DTSTAMP:20140320T214312Z
SEQUENCE:3
UID:bkdiwaiy-cmbs-xjpc-pe24-gd16ybt4mfeu
END:VEVENT
Can I blame this to Business Calendar Pro?
-- Johan
--
Marten Gajda
Schandauer Straße 34
01309 Dresden
Germany
tel: +49 177 4427167
email: marten(a)dmfs.org
twitter: twitter.com/dmfs_org
VAT Reg. No.: DE269072391