Defining Compulsory Data Element Unsuccessfull

Dear Users,

I would like to report the following issue when changing some data elements to be compulsory for the data entry. This DE was already used for a dataset. Please find attached 2 screenshots during the data compulsory edition and the associated unsuccessful message. I am wondering if this is due to the fact that there is already some existing empty values in the data element, or is this issue linked with other consideration?

I am using DHIS2 2.25.

Regards,

Tantely.

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.

image

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 might need to trade with the data that was previously entered using the DE.

Regards

···

On Aug 7, 2017 6:32 PM, “Raminosoa Rabemanantsoa, Tantely” traminosoa@mikolo.org wrote:

Dear Users,

I would like to report the following issue when changing some data elements to be compulsory for the data entry. This DE was already used for a dataset. Please find attached 2 screenshots during the data compulsory edition and the associated unsuccessful message. I am wondering if this is due to the fact that there is already some existing empty values in the data element, or is this issue linked with other consideration?

I am using DHIS2 2.25.

Regards,

Tantely.

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

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,

Tantely.

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.

···

On Mon, Aug 7, 2017 at 8:47 PM, Barnabas Akumba akumbabarns@gmail.com wrote:

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 might need to trade with the data that was previously entered using the DE.

Regards

On Aug 7, 2017 6:32 PM, “Raminosoa Rabemanantsoa, Tantely” traminosoa@mikolo.org wrote:

Dear Users,

I would like to report the following issue when changing some data elements to be compulsory for the data entry. This DE was already used for a dataset. Please find attached 2 screenshots during the data compulsory edition and the associated unsuccessful message. I am wondering if this is due to the fact that there is already some existing empty values in the data element, or is this issue linked with other consideration?

I am using DHIS2 2.25.

Regards,

Tantely.

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

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 Rabemanantsoa, Tantely” traminosoa@mikolo.org wrote:

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,

Tantely.

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.

On Mon, Aug 7, 2017 at 8:47 PM, Barnabas Akumba akumbabarns@gmail.com wrote:

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 might need to trade with the data that was previously entered using the DE.

Regards

On Aug 7, 2017 6:32 PM, “Raminosoa Rabemanantsoa, Tantely” traminosoa@mikolo.org wrote:

Dear Users,

I would like to report the following issue when changing some data elements to be compulsory for the data entry. This DE was already used for a dataset. Please find attached 2 screenshots during the data compulsory edition and the associated unsuccessful message. I am wondering if this is due to the fact that there is already some existing empty values in the data element, or is this issue linked with other consideration?

I am using DHIS2 2.25.

Regards,

Tantely.

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

You’re right! This is the quickest way.

Thank you Barnabas. I could work with this method.

Regards!

Tantely.

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.

···

On Mon, Aug 7, 2017 at 9:11 PM, Barnabas Akumba akumbabarns@gmail.com wrote:

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 Rabemanantsoa, Tantely” traminosoa@mikolo.org wrote:

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,

Tantely.

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.

On Mon, Aug 7, 2017 at 8:47 PM, Barnabas Akumba akumbabarns@gmail.com wrote:

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 might need to trade with the data that was previously entered using the DE.

Regards

On Aug 7, 2017 6:32 PM, “Raminosoa Rabemanantsoa, Tantely” traminosoa@mikolo.org wrote:

Dear Users,

I would like to report the following issue when changing some data elements to be compulsory for the data entry. This DE was already used for a dataset. Please find attached 2 screenshots during the data compulsory edition and the associated unsuccessful message. I am wondering if this is due to the fact that there is already some existing empty values in the data element, or is this issue linked with other consideration?

I am using DHIS2 2.25.

Regards,

Tantely.

This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp