Closed anihojnadel closed 9 years ago
Fixed.
The issue was in the CalendarSerializer in the orc-for-java-shared package. The date returned by the server contains more than 3 milliseconds and SimpleDateFormat only support 3. Those extra milliseconds caused an error in datetime conversion and added some minutes to the orginal date. We removed extra milliseconds and it started working as expected.
The fix will be available in next orc-for-java-shared release (next Thursday 4th of June)
Adding issue from Gary Bentley in: Stack Overflow
I'm finding that a call to Item.getDateTimeLastModified() will consistently return an incorrect date/time. Most of the time, if an item has been recently updated, it will return a millisecond value (in the GMT time zone) that is anything up to 2 hours and a few minutes ahead of current GMT.
Other date times such as Event.getStart()/Event.getEnd() are returning the correct values.
When processing calendar events I am using the following to retrieve events:
Then I process the events one at a time and using the id get the actual event using:
Calling getDateTimeLastModified on that event will return the strange value.
As an aside, I notice that the Office.com calendar when it retrieves the json data for the event has the correct last modified time.