Hi Aravind, I'm sorry, but could you give me some more details.. is this event dataValues? and which timestamp field? is it the one on trackedentitydatavalue? in the even web-api, we are just doing a simple new Date() for data values
If you are talking about programstageinstance, yes, we currently only supports ISO Dates (yyyy-MM-dd), I agree that this should be improved, but it should also not break any existing clients.. -- Morten On Tue, May 27, 2014 at 10:17 AM, Aravind Muralikrishnan < aravi...@thoughtworks.com> wrote: > Hello all, > > We were looking at the API to save DataValues in DHIS. We saw that the > timestamp field in DataValues only stores *date* value in timestamp field > and *ignores the time* part completely before its saved. > > We have a requirement in which we would want to sync the data values at > regular intervals from DHIS through the web api, and we would want the time > part also to be stored in DHIS. > > Is there a specific reason why we are ignoring the time part when saving > DataValues through the API? > > Thanks, > Aravind > > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-devs > Post to : dhis2-devs@lists.launchpad.net > Unsubscribe : https://launchpad.net/~dhis2-devs > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
