dhis2-devs team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

I think this actually is a bug, or at the very least, something quite
confusing to users. The issue here is that IF the data element is not zero
significant, and a user enters a zero. Tim describes a case which is
reproducible, but what happens is not really what is expected. If a user
enters a zero when the DE is not zero significant, then the old value is
not replaced and the old value persists, which is likely not what the user
intended.

 I think the desired action would be
0) Value is changed by the user.
1) Data value is deleted in all cases.
2) Data value is replaced with a new value....
If the data value is zero significant, then the data value is deleted.
If the data value is not zero significant, then the tuple is deleted
entirely.
else, the data value is replaced with the value which the user enters.


I think the problem is that users often do not understand the subtleties of
how zero storage works in DHIS2, so to them, entering a zero basically
means " I am deleting this value". DHIS2 however simply ignores when a zero
is entered all together (at the point of the user interface) and the zero
is never transmitted to the server to determine whether or not the zero
actually needs to be stored. Of course, as you both say, the solution is to
delete the value first, and then enter a zero. My suggestion here would be
that if a user changes a value, then it is first deleted, and then whether
or not the value needs to be stored, would be sorted out in a separate
step.

Regards,
Jason




On Mon, May 19, 2014 at 9:15 AM, <busoye@xxxxxxxx> wrote:

> Hi Hardingt,
>
> This might not be a bug. Check your data elements definition to see if you
> have checked "Save Zero Values". If you have created the data elements as
> zero is not significant then the database will not store zero.
>
> Hope this helps.
>
> Best,
>
> Busoye
>
>
>
> Quoting hardingt <hardingt@xxxxxxxxx>:
>
>  Public bug reported:
>>
>> Replacing a Data Element's value with a 0 will not update the database
>> (Number remains green, and derived indicators also will not update).
>>
>> To circumvent, you must remove the 0 (or whatever number was there) all
>> together so that the data element is now blank. Then it will briefly
>> turn yellow and all indicators based on this data element will
>> automatically update.
>>
>> ** Affects: dhis2
>>      Importance: Undecided
>>          Status: New
>>
>> ** Attachment added: "I put 1, 2, 3, 4 into the fields, then replaced the
>> 4 with a zero."
>>    https://bugs.launchpad.net/bugs/1320755/+attachment/
>> 4115297/+files/Capture.PNG
>>
>> --
>> You received this bug notification because you are a member of DHIS 2
>> developers, which is subscribed to DHIS.
>> https://bugs.launchpad.net/bugs/1320755
>>
>> Title:
>>   Replacing Number with Zero does not update Value in Data Entry
>>
>> Status in DHIS 2:
>>   New
>>
>> Bug description:
>>   Replacing a Data Element's value with a 0 will not update the database
>>   (Number remains green, and derived indicators also will not update).
>>
>>   To circumvent, you must remove the 0 (or whatever number was there)
>>   all together so that the data element is now blank. Then it will
>>   briefly turn yellow and all indicators based on this data element will
>>   automatically update.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/dhis2/+bug/1320755/+subscriptions
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>