Dear Jim
Thank you very much.
It will be very helpful.
On 27 Jan 2017 05:22, "Jim Grace" wrote:
> Hi Nayeem,
>
> Thank you for asking again.
>
> This is now implemented in the latest builds of versions 2.24 and
> following. Negative expiry days are accepted, and the data set is
Hi Jim
Is there any plan to allow dataset lock in advance according to my previous
mail and discussion.
*Nayeem Al Mifthah*
*Consultant for HSS, Health MIS, M*
Email: n.mift...@gmail.com
Cell:+8801914030574
Skype: nayeem.a.m
On Mon, Dec 5, 2016 at 2:53 PM, Nayeem Al Mifthah
Dear Developers
Is there any plan to incorporate data lock in advance as we are using data
set for planning and need to lock before implementation start.
*Nayeem Al Mifthah*
*Consultant for HSS, Health MIS, M*
Email: n.mift...@gmail.com
Cell:+8801914030574
Skype: nayeem.a.m
On Wed, Sep 28, 2016
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
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
5 matches
Mail list logo