Re: [Dhis2-users] [Dhis2-devs] Defining Compulsory Data Element Unsuccessfull

2017-08-07 Thread Raminosoa Rabemanantsoa, Tantely
You're right! This is the quickest way. Thank you Barnabas. I could work with this method. Regards! Tantely. On Mon, Aug 7, 2017 at 9:11 PM, Barnabas Akumba wrote: > Yes. That should be possible if you have access to the DB and you know the > element ID, categoryoptioncombo and attributeopt

Re: [Dhis2-users] [Dhis2-devs] Defining Compulsory Data Element Unsuccessfull

2017-08-07 Thread Barnabas Akumba
Yes. That should be possible if you have access to the DB and you know the element ID, categoryoptioncombo and attributeoptioncombo of both the old and new DEs. The easiest work around for me would be to export the data to CSV and import into the new DE. Regards On Aug 7, 2017 7:03 PM, "Raminosoa

Re: [Dhis2-users] [Dhis2-devs] Defining Compulsory Data Element Unsuccessfull

2017-08-07 Thread Raminosoa Rabemanantsoa, Tantely
Hi Barnabas, Thank you for this straightforward workaround. Would it then possible via SQL view (or another way?) to transfer the existing data of the old DE to the new one? By doing so, we can also set the empty value to an hypothetic one, so that the new DE won't contain any null value. Regards

Re: [Dhis2-users] [Dhis2-devs] Defining Compulsory Data Element Unsuccessfull

2017-08-07 Thread Barnabas Akumba
Hello Raminosoa, The issue is because the Data Element has already been used for data entry and changing the property of the DE at this time will bring about some violations. The solution is to create another DE with the compulsory attribute and remove the previous one from the Dataset. But you m