When updating metadata objects, like data elements, they appear to be updated in the future.
Looking at the API, it seems that the metadata is being returned without a timezone.
Looking at version 2.23, I see
lastUpdated=“2015-01-14T03:35:06.632+0000”
However in version 2.25, this same last updated field appears as
lastUpdated=“2016-02-11T13:10:58.490”
in this case, without a time zone.
Since in this case, the client and server are in different time zones, it appears that the modification was made in the future.
Considering that the lastupdated field is persisted as a time stamp without a time zone, one would assume that this would mean that these fields must be referenced to server time,but when would then need to include the time zone of the server when being transmitted to the client for everything to appear correctly.
Is this a bug?
Regards,
Jason
···
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049