dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #10359
Re: [Bug 717761] Re: 0 value doesn't delete existing data
I think this is not a good idea at all. This could potentially be even
more confusing to users. If zeros are not significant, the system
should just swallow the values (or better yet, persist them to a
datavalue_zeros table, which I am going to write a blueprint for)
silently. Providing this kind of message to the user will 1) just slow
down data entry and 2) be extremely confusing!. Just have the system
either persist the values or not persist them.
Poor old zero...no one likes him but me. :(
On 2/15/11, Nguyen Tran Do Xuan Thuy <thuy.hispvietnam@xxxxxxxxx> wrote:
> Then i think it should show a message that value 0 cannot be save at the
> moment user change it, and the color of text field shouldn't change to green
> color. Because we usually tell user that green color is the sign of data has
> been saved.
>
>
> --
> **Thuy
>
> --
> You received this bug notification because you are a member of DHIS 2
> India Developers, which is subscribed to DHIS.
> https://bugs.launchpad.net/bugs/717761
>
> Title:
> 0 value doesn't delete existing data
>
> Status in DHIS 2 - District Health Information Software:
> Fix Committed
>
> Bug description:
> When entering 0 in a data entry field where a data value already is
> entered, the box turns green, indicating that the value is stored. But
> when "re-visiting" the form the old value is still there. The data
> entry field should be empty!
>
>
>
--
Jason P. Pickering
email: jason.p.pickering@xxxxxxxxx
tel:+260974901293
--
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/717761
Title:
0 value doesn't delete existing data
Status in DHIS 2 - District Health Information Software:
Fix Committed
Bug description:
When entering 0 in a data entry field where a data value already is
entered, the box turns green, indicating that the value is stored. But
when "re-visiting" the form the old value is still there. The data
entry field should be empty!
Follow ups
References