We’re happy to announce the third release candidate of T2A (Tracker to Aggregate). Notable changes include:
Personal Access Token authentication support
Copying the program indicator’s aggregate export attribute option combo to the data value result
Correcting the behaviour where the wrong value is copied into the data value’s category option combo
Renaming the aggr.data.export.de.id parameter to aggr.data.export.attr.id
The application is available for download from the GitHub Release page (see dhis2-t2a.jar). Visit the README file for instructions on how to run the application. Feedback is more than welcome on the CoP.
Period seems to be static. What if I want the period to be dynamic with time? Is there any way out?
There isn’t an inbuilt way to change the period at runtime. Could you expand on this requirement? Maybe you can write a script which wraps around T2A that does this?
Assume, I want to send data to aggregate data element linked with category combo. What is alternative way of doing so ?
Isn’t this only a matter of setting the category option combination for aggregate data export in the program indicator settings as shown here?
Hello @claude.mamo, we are looking into using the T2A tool but having issues getting it to run when scaling it to our data model. We have 1000+ program indicators being pushed to 200+ data elements over the last 12 weeks.
Do you have any advice for us? I only was able to successfully run T2A for the last 4 weeks with 9 PI going into 1 data element. I’ve tried playing with org unit and period batches but haven’t had any success yet.
