Hi again,
I have done an optimization now in trunk r 19326 and 2.19. It seems we
unnecessarily loaded persisted periods for the time span when start and end
dates were used. Please try again on latest trunk and see if it works
better now.
Lars
On Tue, Jun 9, 2015 at 8:21 PM, Lorill Crees wrote
Hi Lars,
Thanks for this. I've tried it out and it's working well in terms of
functionality, but the performance is very poor. Even if I'm limiting to
just one record, one api call is taking 5-7 seconds. When needing to
iterate over 17 datasets this means two minutes for my page load which
would n
Hi Lars
I wonder if you also have any suggestions for checking if data has been
imported for Programs and ProgramStages.
For Programs, I have been doing the following:
/api/enrollments?program=
Get the orgUnit from the first enrollment
/api/trackedEntityInstances?ou=&program=
However,
This has been backported to 2.19 now.
On Tue, Jun 9, 2015 at 11:07 AM, Lars Helge Øverland
wrote:
> Hi Lorill,
>
> I think you have found the best approach to the problem.
>
> I have added support in trunk now for a "limit" query parameter that puts
> a limit on the number of records to return.
Hi Lorill,
I think you have found the best approach to the problem.
I have added support in trunk now for a "limit" query parameter that puts a
limit on the number of records to return. So you can now append "&limit=1"
to your query and check if any records are returned.
I have updated the docs
Hi,
I am trying to craft a web api call to determine if a dataset has at least
one data value in it or not. I am not interested in the data values
themselves, just if any data has been uploaded / inputted into the system
yet or not.
If data values did exist, I would not know what org units or per
6 matches
Mail list logo
