Thanx Morten. Will update
On Mon, Feb 15, 2016 at 8:29 AM, Morten Olav Hansen
wrote:
> Hi Pamod
>
> This should be fixed in latest 2.22/trunk.
>
> On Sun, Feb 14, 2016 at 5:27 PM, Pamod Amarakoon wrote:
>
>> Hi,
>>
>> I noted that time stamp in trackedEntityInstances resource has both
>> DHIS2/
Hi Pamod
This should be fixed in latest 2.22/trunk.
On Sun, Feb 14, 2016 at 5:27 PM, Pamod Amarakoon wrote:
> Hi,
>
> I noted that time stamp in trackedEntityInstances resource has both
> DHIS2/server timestamp and ISO time stamp (in UTC) as below.
>
> {
>
> "lastUpdated": "2016-02-14 15:43
Hi,
I noted that time stamp in trackedEntityInstances resource has both
DHIS2/server timestamp and ISO time stamp (in UTC) as below.
{
"lastUpdated": "2016-02-14 15:43:35.087", <- Server time
"trackedEntity": "kuWSv1dRXIm",
"created": "2016-01-02 19:28:36.192",
"orgUnit": "w
Hi Pamod
The convention is to generally do this on the client-side. If the Web API
is *correctly converting* local timezone to UTC and you see + at the
end of timestamps, it means the client can change this to whatever timezone
its supposed to be in. That seems to be the appropriate approach si
Dear All,
I currently have an instance of which server timezone, Postgresql time zone
and java time zone has been set to Asia/Colombo. I can see the data been
stored in database in local time stamp.
But when retrieving data through web API time stamp is in UTC. Is it
possible to change the timest
5 matches
Mail list logo