Hi,
I presume you want the data set exported with allocated orgunits
The main drawback with randomly generated numbers is that a lot of things
won't make any sense with such data, like data validation rules and
indicators. It will work for certain types of "techie" testing only -
health worke
Perfectly agree with you. The generation of fake data can be based on a
more comprehensive set of meta-data, instead of just the dataSets.
I think that further development could solve the problem.
At the moment the application solves the main hassle: assembles the
combination of dataElements Ids
Hi Lars,
We are having this problem also using 2.22 revision 22000 (maybe it was
corrected in later 2.22 versions? ). So the problem happens when we import
a bulk of dataelements from an XML file, and we call ../api/me/programs
if we restart the tomcat (not a good practice :) ) the API call work
The confusion in adding the trackedEntity was whether it would be a child
of the trackedEntityInstance or not.
Furthermore a 3rd parameter of the Orgunit ID was required. So I was
wondering whether 'Chapter 1.53 Tracker bulk deletion' (
http://dhis2.github.io/dhis2-docs/2.22/en/developer/html/ch01
Any help on this?
Regards
Pramil
On Sat, May 7, 2016 at 8:53 PM, Pramil Liyanage wrote:
> Thanks Lars. Let me summarize my issue. We have been using aggregated
> reporting for TB for a few years and recently introduced individual records
> and aggregated using query builder to the same aggregat
On Mon, May 9, 2016 at 5:22 AM, Jose Garcia Muñoz
wrote:
>
> Hi Lars,
>
> We are having this problem also using 2.22 revision 22000 (maybe it was
> corrected in later 2.22 versions? ). So the problem happens when we import
> a bulk of dataelements from an XML file, and we call ../api/me/programs
6 matches
Mail list logo
