On demo, if an event has had data entered then the dataValues fields will contain all the dataValues. But this does not happen on the dev server, Even if an event has data then also the dataValues is just coming as empty tag.
PFA snapshot comparing demo with dev.
Also, adding ‘skipPaging=true’ to the above URL endpoint results in 504 Gateway Time-out. And the instance goes down for a while. This happens on both demo and dev.
Thanks
harsh
···
On 24 February 2016 at 19:50, Lars Helge Øverland lars@dhis2.org wrote:
Hi Harsh,
we need more information from you in order to help. Can you reproduce on demo? Did you have a look at the docs for event queries?
Yes there is a change with the API. Morten can provide more details on this
For now, you can use the following and get data values api/events.json?fields=:all,dataValues[value,dataElement],notes[value,storedBy,storedDate]
By skipping paging you are literally asking for all events in the db - which is huge and no wonder the time out response. This should be blocked. I mean it shouldn’t be possible to just ask for events without specifying some parameters - for example orgunit, program, tei, enrollment…
···
What is your use-case? Can you limit the search for events?
On demo, if an event has had data entered then the dataValues fields will contain all the dataValues. But this does not happen on the dev server, Even if an event has data then also the dataValues is just coming as empty tag.
PFA snapshot comparing demo with dev.
Also, adding ‘skipPaging=true’ to the above URL endpoint results in 504 Gateway Time-out. And the instance goes down for a while. This happens on both demo and dev.