Re: [Dhis2-users] Error when exporting metadata throuhg metadata export

2017-11-17 Thread Knut Staring
Hello Vunda, Whenever you get a 500 Internal Server Error, you have too look at (and probrobably share) your Tomcat server log, which should contain more interesting error messages. Regards, Knut On Fri, Nov 17, 2017 at 1:57 PM, vunda limbe wrote: > Hi Everybody, > > When

[Dhis2-users] Mark Dataset Complete

2017-11-17 Thread Raja Imran Qamer
Hi everybody, I have saved data for a dataset but did not mark it complete, now i want to mark all saved data complete, I am trying to do so using myurl/api/26/completeDataSetRegistrations Response i receives

[Dhis2-users] Error when exporting metadata throuhg metadata export

2017-11-17 Thread vunda limbe
Hi Everybody, When I try to export meta data in both json or xml, I'm getting this message: " {"httpStatus":"Internal Server Error","httpStatusCode":500,"status":"ERROR"} Could someone tell me how to fix this? Alternativly, someone can give me a script in order to export dataelement, COC, CO

Re: [Dhis2-users] Tracker programs and unique IDs

2017-11-17 Thread Stanley Kalyati
Thanks Prosper Very informative. On Nov 17, 2017 10:48 AM, "Prosper BT" wrote: > Dear Edward and Stanley > > Currently we have attribute Unique Identifiers with just simply random > generated number that could be set to be unique within Orgunits or entire > system. This is

Re: [Dhis2-users] Tracker programs and unique IDs

2017-11-17 Thread Edward Robinson
Thanks for the feedback Prosper, I’ll take a look at the Jira issue. @Thierry Octave Regards Ed From: Prosper BT [mailto:ptb3...@gmail.com] Sent: Friday, 17 November 2017 10:47 AM To: Stanley Kalyati Cc: Edward Robinson

Re: [Dhis2-users] Tracker programs and unique IDs

2017-11-17 Thread Prosper BT
Dear Edward and Stanley Currently we have attribute Unique Identifiers with just simply random generated number that could be set to be unique within Orgunits or entire system. This is being expanded to address your need to customize to the use cases pattern; check jira issue (DHIS2-434