This message is for API or data forwarding users only. If you are just
using CommCare mobile and CommCare HQ there is no need to read this
message.
In the next few weeks, we will be rolling out changes to our underlying
serialization systems so that we can store more precise timestamps, up to
the microsecond. For the most part, this will happen completely
transparently, but in the case of our Data APIs and Data Forwarding, it
means you should expect dates to arrive like
2015-04-17T20:14:34.046462Z
instead of like
2015-04-17T20:14:34Z
We wanted to give you advance notice so you could make any changes
accordingly. Our advice is to make sure your processing software is capable
of consuming both formats, so that the change will be seamless to you.
If you have any questions or concerns about this don't hesitate to report
an issue and someone on our team will help you understand the implications
and talk through how to upgrade.
ยทยทยท
On Mon, Apr 20, 2015 at 2:17 PM, Cory Zue wrote:
Dear Users,
This message is for API or data forwarding users only. If you are just
using CommCare mobile and CommCare HQ there is no need to read this
message.
In the next few weeks, we will be rolling out changes to our underlying
serialization systems so that we can store more precise timestamps, up to
the microsecond. For the most part, this will happen completely
transparently, but in the case of our Data APIs and Data Forwarding, it
means you should expect dates to arrive like
2015-04-17T20:14:34.046462Z
instead of like
2015-04-17T20:14:34Z
We wanted to give you advance notice so you could make any changes
accordingly. Our advice is to make sure your processing software is capable
of consuming both formats, so that the change will be seamless to you.
If you have any questions or concerns about this don't hesitate to report
an issue and someone on our team will help you understand the implications
and talk through how to upgrade.