Unique tracked entity attributes are now compulsory?

Dear devs,

we realized that tracked attributes are always compulsory even if they are not marked like that in the program definition? so it is not possible at all to keep them blank using the Tracker Capture.

In PSI (and I guess is the same for many different countries), we need to define unique patient’s IDs, although several times it is not possible to collect them for many reasons, but now the system is not giving us the option of keeping the IDs blank

Is this something that can be changed? Unique attributes can be compulsory just marking the attribute as compulsory in the program definition…

Please, let us know, as we may need to reconsider some re-configuration for our programs.

Many Thanks

Jose

Hi

Sorry for late reply, but I have been looking into this, and from the backend this is not required. I’m adding in Abyot, hopefully he can answer why it is required in the UI part (I see it’s marked with red star, and it will not allow it without a value)

···

On Mon, Jun 6, 2016 at 12:02 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear devs,

we realized that tracked attributes are always compulsory even if they are not marked like that in the program definition? so it is not possible at all to keep them blank using the Tracker Capture.

In PSI (and I guess is the same for many different countries), we need to define unique patient’s IDs, although several times it is not possible to collect them for many reasons, but now the system is not giving us the option of keeping the IDs blank

Is this something that can be changed? Unique attributes can be compulsory just marking the attribute as compulsory in the program definition…

Please, let us know, as we may need to reconsider some re-configuration for our programs.

Many Thanks

Jose


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

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

Hi guys!

Chiming in - I think Abyot is on leave today.
This seems to be a discrepancy that we should just resolve one way or the other. You might say that a blank value is not unique, but I have also recently encountered a use case where we needed a non-compulsory unique attribute like you Jose.

Hiding the field with program rules was a workaround in our case, but I think it makes sense to allow blank values in non-compulsory unique attributes.

Unless there is any disagreements we can implement the client to conform to the API.

Markus

···

On Mon, Jun 6, 2016 at 12:02 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear devs,

we realized that tracked attributes are always compulsory even if they are not marked like that in the program definition? so it is not possible at all to keep them blank using the Tracker Capture.

In PSI (and I guess is the same for many different countries), we need to define unique patient’s IDs, although several times it is not possible to collect them for many reasons, but now the system is not giving us the option of keeping the IDs blank

Is this something that can be changed? Unique attributes can be compulsory just marking the attribute as compulsory in the program definition…

Please, let us know, as we may need to reconsider some re-configuration for our programs.

Many Thanks

Jose


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

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

Hi Markus

I had a short email exchange with Abyot last week and he said the same "So many blanks can not be unique” but for a value to be unique there must be a value. If the database and the API do not have this requirement, the interface should follow the program’s configuration.

Best regards,

JM

···

On Mon, Jun 6, 2016 at 12:02 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear devs,

we realized that tracked attributes are always compulsory even if they are not marked like that in the program definition? so it is not possible at all to keep them blank using the Tracker Capture.

In PSI (and I guess is the same for many different countries), we need to define unique patient’s IDs, although several times it is not possible to collect them for many reasons, but now the system is not giving us the option of keeping the IDs blank

Is this something that can be changed? Unique attributes can be compulsory just marking the attribute as compulsory in the program definition…

Please, let us know, as we may need to reconsider some re-configuration for our programs.

Many Thanks

Jose


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

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

I just want to support the idea that blanks should be accepted and not checked for uniqueness. I’m glad to hear that the API already supports this, so it will be great if the UI follows that logic.

···

On 8 June 2016 at 10:49, Juan Manuel Alcantara Acosta jmalcantara1@gmail.com wrote:

Hi Markus
I had a short email exchange with Abyot last week and he said the same "So many blanks can not be unique” but for a value to be unique there must be a value. If the database and the API do not have this requirement, the interface should follow the program’s configuration.

Best regards,

JM

El 08/06/2016, a las 8:35 a.m., Markus Bekken markus.bekken@gmail.com escribió:

Hi guys!
Chiming in - I think Abyot is on leave today.
This seems to be a discrepancy that we should just resolve one way or the other. You might say that a blank value is not unique, but I have also recently encountered a use case where we needed a non-compulsory unique attribute like you Jose.

Hiding the field with program rules was a workaround in our case, but I think it makes sense to allow blank values in non-compulsory unique attributes.

Unless there is any disagreements we can implement the client to conform to the API.

Markus

  1. jun. 2016 kl. 09.15 skrev Morten Olav Hansen morten@dhis2.org:

Hi

Sorry for late reply, but I have been looking into this, and from the backend this is not required. I’m adding in Abyot, hopefully he can answer why it is required in the UI part (I see it’s marked with red star, and it will not allow it without a value)


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


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


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

**Rodolfo **

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Jun 6, 2016 at 12:02 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear devs,

we realized that tracked attributes are always compulsory even if they are not marked like that in the program definition? so it is not possible at all to keep them blank using the Tracker Capture.

In PSI (and I guess is the same for many different countries), we need to define unique patient’s IDs, although several times it is not possible to collect them for many reasons, but now the system is not giving us the option of keeping the IDs blank

Is this something that can be changed? Unique attributes can be compulsory just marking the attribute as compulsory in the program definition…

Please, let us know, as we may need to reconsider some re-configuration for our programs.

Many Thanks

Jose


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 guys,

any agreements on this? :slight_smile:

I would like to know if I need to change the configuration of some programs (unique attributes are always compulsory) or not (unique attributes can be optional). I would prefer if we can keep them blank as well (so they are optional).

Thanks

Jose

···

On Wed, Jun 8, 2016 at 10:52 AM, Rodolfo Melia rmelia@knowming.com wrote:

I just want to support the idea that blanks should be accepted and not checked for uniqueness. I’m glad to hear that the API already supports this, so it will be great if the UI follows that logic.


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

**Rodolfo **

On 8 June 2016 at 10:49, Juan Manuel Alcantara Acosta jmalcantara1@gmail.com wrote:

Hi Markus
I had a short email exchange with Abyot last week and he said the same "So many blanks can not be unique” but for a value to be unique there must be a value. If the database and the API do not have this requirement, the interface should follow the program’s configuration.

Best regards,

JM

El 08/06/2016, a las 8:35 a.m., Markus Bekken markus.bekken@gmail.com escribió:

Hi guys!
Chiming in - I think Abyot is on leave today.
This seems to be a discrepancy that we should just resolve one way or the other. You might say that a blank value is not unique, but I have also recently encountered a use case where we needed a non-compulsory unique attribute like you Jose.

Hiding the field with program rules was a workaround in our case, but I think it makes sense to allow blank values in non-compulsory unique attributes.

Unless there is any disagreements we can implement the client to conform to the API.

Markus

  1. jun. 2016 kl. 09.15 skrev Morten Olav Hansen morten@dhis2.org:

Hi

Sorry for late reply, but I have been looking into this, and from the backend this is not required. I’m adding in Abyot, hopefully he can answer why it is required in the UI part (I see it’s marked with red star, and it will not allow it without a value)


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


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


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

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Jun 6, 2016 at 12:02 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear devs,

we realized that tracked attributes are always compulsory even if they are not marked like that in the program definition? so it is not possible at all to keep them blank using the Tracker Capture.

In PSI (and I guess is the same for many different countries), we need to define unique patient’s IDs, although several times it is not possible to collect them for many reasons, but now the system is not giving us the option of keeping the IDs blank

Is this something that can be changed? Unique attributes can be compulsory just marking the attribute as compulsory in the program definition…

Please, let us know, as we may need to reconsider some re-configuration for our programs.

Many Thanks

Jose


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,

I think I missed that it was not required from the server side api … it is easy to fix from the client side.

···

On Fri, Jun 10, 2016 at 4:59 AM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Hi guys,

any agreements on this? :slight_smile:

I would like to know if I need to change the configuration of some programs (unique attributes are always compulsory) or not (unique attributes can be optional). I would prefer if we can keep them blank as well (so they are optional).

Thanks

Jose


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

Abyot A. Gizaw.

Senior Engineer, DHIS2

University of Oslo

http://www.dhis2.org

On Wed, Jun 8, 2016 at 10:52 AM, Rodolfo Melia rmelia@knowming.com wrote:

I just want to support the idea that blanks should be accepted and not checked for uniqueness. I’m glad to hear that the API already supports this, so it will be great if the UI follows that logic.


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

**Rodolfo **

On 8 June 2016 at 10:49, Juan Manuel Alcantara Acosta jmalcantara1@gmail.com wrote:

Hi Markus
I had a short email exchange with Abyot last week and he said the same "So many blanks can not be unique” but for a value to be unique there must be a value. If the database and the API do not have this requirement, the interface should follow the program’s configuration.

Best regards,

JM

El 08/06/2016, a las 8:35 a.m., Markus Bekken markus.bekken@gmail.com escribió:

Hi guys!
Chiming in - I think Abyot is on leave today.
This seems to be a discrepancy that we should just resolve one way or the other. You might say that a blank value is not unique, but I have also recently encountered a use case where we needed a non-compulsory unique attribute like you Jose.

Hiding the field with program rules was a workaround in our case, but I think it makes sense to allow blank values in non-compulsory unique attributes.

Unless there is any disagreements we can implement the client to conform to the API.

Markus

  1. jun. 2016 kl. 09.15 skrev Morten Olav Hansen morten@dhis2.org:

Hi

Sorry for late reply, but I have been looking into this, and from the backend this is not required. I’m adding in Abyot, hopefully he can answer why it is required in the UI part (I see it’s marked with red star, and it will not allow it without a value)


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


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


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

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Jun 6, 2016 at 12:02 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear devs,

we realized that tracked attributes are always compulsory even if they are not marked like that in the program definition? so it is not possible at all to keep them blank using the Tracker Capture.

In PSI (and I guess is the same for many different countries), we need to define unique patient’s IDs, although several times it is not possible to collect them for many reasons, but now the system is not giving us the option of keeping the IDs blank

Is this something that can be changed? Unique attributes can be compulsory just marking the attribute as compulsory in the program definition…

Please, let us know, as we may need to reconsider some re-configuration for our programs.

Many Thanks

Jose


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 there,

seems we agree, just wanted to add that we should always trim blank values to null before storing, and nulls are not in conflict with uniqueness.

Lars

···

On Fri, Jun 10, 2016 at 7:29 AM, Abyot Asalefew Gizaw abyot@dhis2.org wrote:

Hi,

I think I missed that it was not required from the server side api … it is easy to fix from the client side.


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

Abyot A. Gizaw.

Senior Engineer, DHIS2

University of Oslo

http://www.dhis2.org

On Fri, Jun 10, 2016 at 4:59 AM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Hi guys,

any agreements on this? :slight_smile:

I would like to know if I need to change the configuration of some programs (unique attributes are always compulsory) or not (unique attributes can be optional). I would prefer if we can keep them blank as well (so they are optional).

Thanks

Jose


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

On Wed, Jun 8, 2016 at 10:52 AM, Rodolfo Melia rmelia@knowming.com wrote:

I just want to support the idea that blanks should be accepted and not checked for uniqueness. I’m glad to hear that the API already supports this, so it will be great if the UI follows that logic.


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

**Rodolfo **

On 8 June 2016 at 10:49, Juan Manuel Alcantara Acosta jmalcantara1@gmail.com wrote:

Hi Markus
I had a short email exchange with Abyot last week and he said the same "So many blanks can not be unique” but for a value to be unique there must be a value. If the database and the API do not have this requirement, the interface should follow the program’s configuration.

Best regards,

JM

El 08/06/2016, a las 8:35 a.m., Markus Bekken markus.bekken@gmail.com escribió:

Hi guys!
Chiming in - I think Abyot is on leave today.
This seems to be a discrepancy that we should just resolve one way or the other. You might say that a blank value is not unique, but I have also recently encountered a use case where we needed a non-compulsory unique attribute like you Jose.

Hiding the field with program rules was a workaround in our case, but I think it makes sense to allow blank values in non-compulsory unique attributes.

Unless there is any disagreements we can implement the client to conform to the API.

Markus

  1. jun. 2016 kl. 09.15 skrev Morten Olav Hansen morten@dhis2.org:

Hi

Sorry for late reply, but I have been looking into this, and from the backend this is not required. I’m adding in Abyot, hopefully he can answer why it is required in the UI part (I see it’s marked with red star, and it will not allow it without a value)


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


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


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

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Jun 6, 2016 at 12:02 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear devs,

we realized that tracked attributes are always compulsory even if they are not marked like that in the program definition? so it is not possible at all to keep them blank using the Tracker Capture.

In PSI (and I guess is the same for many different countries), we need to define unique patient’s IDs, although several times it is not possible to collect them for many reasons, but now the system is not giving us the option of keeping the IDs blank

Is this something that can be changed? Unique attributes can be compulsory just marking the attribute as compulsory in the program definition…

Please, let us know, as we may need to reconsider some re-configuration for our programs.

Many Thanks

Jose


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

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Look forward to check the next 2.22 build with the updated feature. Please let us know from what 2.22 build we can start testing.

···

On 10 June 2016 at 07:56, Lars Helge Øverland lars@dhis2.org wrote:

Hi there,

seems we agree, just wanted to add that we should always trim blank values to null before storing, and nulls are not in conflict with uniqueness.

Lars


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

Rodolfo Meliá

*Principal | *rmelia@knowming.com

Skype: rod.melia | +44 777 576 4090 | +1 708 872 7636

www.knowming.com

On Fri, Jun 10, 2016 at 7:29 AM, Abyot Asalefew Gizaw abyot@dhis2.org wrote:

Hi,

I think I missed that it was not required from the server side api … it is easy to fix from the client side.


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

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Abyot A. Gizaw.

Senior Engineer, DHIS2

University of Oslo

http://www.dhis2.org

On Fri, Jun 10, 2016 at 4:59 AM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Hi guys,

any agreements on this? :slight_smile:

I would like to know if I need to change the configuration of some programs (unique attributes are always compulsory) or not (unique attributes can be optional). I would prefer if we can keep them blank as well (so they are optional).

Thanks

Jose


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

On Wed, Jun 8, 2016 at 10:52 AM, Rodolfo Melia rmelia@knowming.com wrote:

I just want to support the idea that blanks should be accepted and not checked for uniqueness. I’m glad to hear that the API already supports this, so it will be great if the UI follows that logic.


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

**Rodolfo **

On 8 June 2016 at 10:49, Juan Manuel Alcantara Acosta jmalcantara1@gmail.com wrote:

Hi Markus
I had a short email exchange with Abyot last week and he said the same "So many blanks can not be unique” but for a value to be unique there must be a value. If the database and the API do not have this requirement, the interface should follow the program’s configuration.

Best regards,

JM

El 08/06/2016, a las 8:35 a.m., Markus Bekken markus.bekken@gmail.com escribió:

Hi guys!
Chiming in - I think Abyot is on leave today.
This seems to be a discrepancy that we should just resolve one way or the other. You might say that a blank value is not unique, but I have also recently encountered a use case where we needed a non-compulsory unique attribute like you Jose.

Hiding the field with program rules was a workaround in our case, but I think it makes sense to allow blank values in non-compulsory unique attributes.

Unless there is any disagreements we can implement the client to conform to the API.

Markus

  1. jun. 2016 kl. 09.15 skrev Morten Olav Hansen morten@dhis2.org:

Hi

Sorry for late reply, but I have been looking into this, and from the backend this is not required. I’m adding in Abyot, hopefully he can answer why it is required in the UI part (I see it’s marked with red star, and it will not allow it without a value)


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


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


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

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Jun 6, 2016 at 12:02 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear devs,

we realized that tracked attributes are always compulsory even if they are not marked like that in the program definition? so it is not possible at all to keep them blank using the Tracker Capture.

In PSI (and I guess is the same for many different countries), we need to define unique patient’s IDs, although several times it is not possible to collect them for many reasons, but now the system is not giving us the option of keeping the IDs blank

Is this something that can be changed? Unique attributes can be compulsory just marking the attribute as compulsory in the program definition…

Please, let us know, as we may need to reconsider some re-configuration for our programs.

Many Thanks

Jose


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,

A fix is committed for this. Rev. 22063 and above should work…

···

On Fri, Jun 10, 2016 at 1:44 PM, Rodolfo Melia rmelia@knowming.com wrote:

Look forward to check the next 2.22 build with the updated feature. Please let us know from what 2.22 build we can start testing.

Abyot A. Gizaw.

Senior Engineer, DHIS2

University of Oslo

http://www.dhis2.org

Rodolfo Meliá

*Principal | *rmelia@knowming.com

Skype: rod.melia | +44 777 576 4090 | +1 708 872 7636

www.knowming.com

On 10 June 2016 at 07:56, Lars Helge Øverland lars@dhis2.org wrote:

Hi there,

seems we agree, just wanted to add that we should always trim blank values to null before storing, and nulls are not in conflict with uniqueness.

Lars


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

On Fri, Jun 10, 2016 at 7:29 AM, Abyot Asalefew Gizaw abyot@dhis2.org wrote:

Hi,

I think I missed that it was not required from the server side api … it is easy to fix from the client side.


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

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Abyot A. Gizaw.

Senior Engineer, DHIS2

University of Oslo

http://www.dhis2.org

On Fri, Jun 10, 2016 at 4:59 AM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Hi guys,

any agreements on this? :slight_smile:

I would like to know if I need to change the configuration of some programs (unique attributes are always compulsory) or not (unique attributes can be optional). I would prefer if we can keep them blank as well (so they are optional).

Thanks

Jose


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

On Wed, Jun 8, 2016 at 10:52 AM, Rodolfo Melia rmelia@knowming.com wrote:

I just want to support the idea that blanks should be accepted and not checked for uniqueness. I’m glad to hear that the API already supports this, so it will be great if the UI follows that logic.


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

**Rodolfo **

On 8 June 2016 at 10:49, Juan Manuel Alcantara Acosta jmalcantara1@gmail.com wrote:

Hi Markus
I had a short email exchange with Abyot last week and he said the same "So many blanks can not be unique” but for a value to be unique there must be a value. If the database and the API do not have this requirement, the interface should follow the program’s configuration.

Best regards,

JM

El 08/06/2016, a las 8:35 a.m., Markus Bekken markus.bekken@gmail.com escribió:

Hi guys!
Chiming in - I think Abyot is on leave today.
This seems to be a discrepancy that we should just resolve one way or the other. You might say that a blank value is not unique, but I have also recently encountered a use case where we needed a non-compulsory unique attribute like you Jose.

Hiding the field with program rules was a workaround in our case, but I think it makes sense to allow blank values in non-compulsory unique attributes.

Unless there is any disagreements we can implement the client to conform to the API.

Markus

  1. jun. 2016 kl. 09.15 skrev Morten Olav Hansen morten@dhis2.org:

Hi

Sorry for late reply, but I have been looking into this, and from the backend this is not required. I’m adding in Abyot, hopefully he can answer why it is required in the UI part (I see it’s marked with red star, and it will not allow it without a value)


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


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


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

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Jun 6, 2016 at 12:02 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear devs,

we realized that tracked attributes are always compulsory even if they are not marked like that in the program definition? so it is not possible at all to keep them blank using the Tracker Capture.

In PSI (and I guess is the same for many different countries), we need to define unique patient’s IDs, although several times it is not possible to collect them for many reasons, but now the system is not giving us the option of keeping the IDs blank

Is this something that can be changed? Unique attributes can be compulsory just marking the attribute as compulsory in the program definition…

Please, let us know, as we may need to reconsider some re-configuration for our programs.

Many Thanks

Jose


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

Fantastic! Many thanks Abyot

···

On Sun, Jun 12, 2016 at 2:09 PM, Abyot Asalefew Gizaw abyot@dhis2.org wrote:

Hi,

A fix is committed for this. Rev. 22063 and above should work…


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

Abyot A. Gizaw.

Senior Engineer, DHIS2

University of Oslo

http://www.dhis2.org

On Fri, Jun 10, 2016 at 1:44 PM, Rodolfo Melia rmelia@knowming.com wrote:

Look forward to check the next 2.22 build with the updated feature. Please let us know from what 2.22 build we can start testing.

Rodolfo Meliá

*Principal | *rmelia@knowming.com

Skype: rod.melia | +44 777 576 4090 | +1 708 872 7636

www.knowming.com

On 10 June 2016 at 07:56, Lars Helge Øverland lars@dhis2.org wrote:

Hi there,

seems we agree, just wanted to add that we should always trim blank values to null before storing, and nulls are not in conflict with uniqueness.

Lars


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

On Fri, Jun 10, 2016 at 7:29 AM, Abyot Asalefew Gizaw abyot@dhis2.org wrote:

Hi,

I think I missed that it was not required from the server side api … it is easy to fix from the client side.


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

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Abyot A. Gizaw.

Senior Engineer, DHIS2

University of Oslo

http://www.dhis2.org

On Fri, Jun 10, 2016 at 4:59 AM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Hi guys,

any agreements on this? :slight_smile:

I would like to know if I need to change the configuration of some programs (unique attributes are always compulsory) or not (unique attributes can be optional). I would prefer if we can keep them blank as well (so they are optional).

Thanks

Jose


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

On Wed, Jun 8, 2016 at 10:52 AM, Rodolfo Melia rmelia@knowming.com wrote:

I just want to support the idea that blanks should be accepted and not checked for uniqueness. I’m glad to hear that the API already supports this, so it will be great if the UI follows that logic.


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

**Rodolfo **

On 8 June 2016 at 10:49, Juan Manuel Alcantara Acosta jmalcantara1@gmail.com wrote:

Hi Markus
I had a short email exchange with Abyot last week and he said the same "So many blanks can not be unique” but for a value to be unique there must be a value. If the database and the API do not have this requirement, the interface should follow the program’s configuration.

Best regards,

JM

El 08/06/2016, a las 8:35 a.m., Markus Bekken markus.bekken@gmail.com escribió:

Hi guys!
Chiming in - I think Abyot is on leave today.
This seems to be a discrepancy that we should just resolve one way or the other. You might say that a blank value is not unique, but I have also recently encountered a use case where we needed a non-compulsory unique attribute like you Jose.

Hiding the field with program rules was a workaround in our case, but I think it makes sense to allow blank values in non-compulsory unique attributes.

Unless there is any disagreements we can implement the client to conform to the API.

Markus

  1. jun. 2016 kl. 09.15 skrev Morten Olav Hansen morten@dhis2.org:

Hi

Sorry for late reply, but I have been looking into this, and from the backend this is not required. I’m adding in Abyot, hopefully he can answer why it is required in the UI part (I see it’s marked with red star, and it will not allow it without a value)


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


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


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

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Jun 6, 2016 at 12:02 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear devs,

we realized that tracked attributes are always compulsory even if they are not marked like that in the program definition? so it is not possible at all to keep them blank using the Tracker Capture.

In PSI (and I guess is the same for many different countries), we need to define unique patient’s IDs, although several times it is not possible to collect them for many reasons, but now the system is not giving us the option of keeping the IDs blank

Is this something that can be changed? Unique attributes can be compulsory just marking the attribute as compulsory in the program definition…

Please, let us know, as we may need to reconsider some re-configuration for our programs.

Many Thanks

Jose


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

Thanks Abyot ! - will test and get back to you if we have any problems.

···

On 12 June 2016 at 13:09, Abyot Asalefew Gizaw abyot@dhis2.org wrote:

Hi,

A fix is committed for this. Rev. 22063 and above should work…

Rodolfo Meliá

*Principal | *rmelia@knowming.com

Skype: rod.melia | +44 777 576 4090 | +1 708 872 7636

www.knowming.com

Abyot A. Gizaw.

Senior Engineer, DHIS2

University of Oslo

http://www.dhis2.org

On Fri, Jun 10, 2016 at 1:44 PM, Rodolfo Melia rmelia@knowming.com wrote:

Look forward to check the next 2.22 build with the updated feature. Please let us know from what 2.22 build we can start testing.

Rodolfo Meliá

*Principal | *rmelia@knowming.com

Skype: rod.melia | +44 777 576 4090 | +1 708 872 7636

www.knowming.com

On 10 June 2016 at 07:56, Lars Helge Øverland lars@dhis2.org wrote:

Hi there,

seems we agree, just wanted to add that we should always trim blank values to null before storing, and nulls are not in conflict with uniqueness.

Lars


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

On Fri, Jun 10, 2016 at 7:29 AM, Abyot Asalefew Gizaw abyot@dhis2.org wrote:

Hi,

I think I missed that it was not required from the server side api … it is easy to fix from the client side.


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

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Abyot A. Gizaw.

Senior Engineer, DHIS2

University of Oslo

http://www.dhis2.org

On Fri, Jun 10, 2016 at 4:59 AM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Hi guys,

any agreements on this? :slight_smile:

I would like to know if I need to change the configuration of some programs (unique attributes are always compulsory) or not (unique attributes can be optional). I would prefer if we can keep them blank as well (so they are optional).

Thanks

Jose


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

On Wed, Jun 8, 2016 at 10:52 AM, Rodolfo Melia rmelia@knowming.com wrote:

I just want to support the idea that blanks should be accepted and not checked for uniqueness. I’m glad to hear that the API already supports this, so it will be great if the UI follows that logic.


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

**Rodolfo **

On 8 June 2016 at 10:49, Juan Manuel Alcantara Acosta jmalcantara1@gmail.com wrote:

Hi Markus
I had a short email exchange with Abyot last week and he said the same "So many blanks can not be unique” but for a value to be unique there must be a value. If the database and the API do not have this requirement, the interface should follow the program’s configuration.

Best regards,

JM

El 08/06/2016, a las 8:35 a.m., Markus Bekken markus.bekken@gmail.com escribió:

Hi guys!
Chiming in - I think Abyot is on leave today.
This seems to be a discrepancy that we should just resolve one way or the other. You might say that a blank value is not unique, but I have also recently encountered a use case where we needed a non-compulsory unique attribute like you Jose.

Hiding the field with program rules was a workaround in our case, but I think it makes sense to allow blank values in non-compulsory unique attributes.

Unless there is any disagreements we can implement the client to conform to the API.

Markus

  1. jun. 2016 kl. 09.15 skrev Morten Olav Hansen morten@dhis2.org:

Hi

Sorry for late reply, but I have been looking into this, and from the backend this is not required. I’m adding in Abyot, hopefully he can answer why it is required in the UI part (I see it’s marked with red star, and it will not allow it without a value)


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


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


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

Morten Olav Hansen

Senior Engineer, DHIS 2

University of Oslo

http://www.dhis2.org

On Mon, Jun 6, 2016 at 12:02 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:

Dear devs,

we realized that tracked attributes are always compulsory even if they are not marked like that in the program definition? so it is not possible at all to keep them blank using the Tracker Capture.

In PSI (and I guess is the same for many different countries), we need to define unique patient’s IDs, although several times it is not possible to collect them for many reasons, but now the system is not giving us the option of keeping the IDs blank

Is this something that can be changed? Unique attributes can be compulsory just marking the attribute as compulsory in the program definition…

Please, let us know, as we may need to reconsider some re-configuration for our programs.

Many Thanks

Jose


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