dhis2-users team mailing list archive

[Jim Grace <jim@xxxxxxxxx>]

Agreed, it would be good if negative values were accepted and processed.
This could be useful for one of our other implementations as well, that I'm
working on.

Meanwhile, another possibility is to use data approvals to lock out data
entry for the future period. It would involve taking action every time you
want the future data locked, but it would do that. See
http://dhis2.github.io/dhis2-docs/master/en/user/html/data_approvals.html.


On Wed, Sep 28, 2016 at 2:12 AM, Nayeem Al Mifthah <n.mifthah@xxxxxxxxx>
wrote:

> Dear All
> We are using DHIS2 for planning purposes. For this organizations are input
> plan in advance. We want to lock the dataset in advance.
>
>
> Like now we want to lock the next quarter planning data entry before 15
> days from starting of next quarter. But data lock is not taking negative
> (-) value in dataset design.
>
>
> *Nayeem Al Mifthah*
> *Consultant for HSS, Health MIS, M&E*
> Email: n.mifthah@xxxxxxxxx
> Cell:+8801914030574
> Skype: nayeem.a.m
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Jim Grace
Core developer, DHIS 2
HISP US Inc.
http://www.dhis2.org <https://www.dhis2.org/>