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 locked before the end of the period. With a large enough negative expiry day count, the data set can be locked as far ahead as you like, even before the start of the period. As you said, this can be useful for entering future data such as for planning, forecasting, or targets. Cheers, Jim On Mon, Jan 23, 2017 at 1:20 AM, Nayeem Al Mifthah <[email protected]> wrote: > 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&E* > Email: [email protected] > Cell:+8801914030574 <+880%201914-030574> > Skype: nayeem.a.m > > On Mon, Dec 5, 2016 at 2:53 PM, Nayeem Al Mifthah <[email protected]> > wrote: > >> 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&E* >> Email: [email protected] >> Cell:+8801914030574 <01914-030574> >> Skype: nayeem.a.m >> >> On Wed, Sep 28, 2016 at 5:24 PM, Jim Grace <[email protected]> wrote: >> >>> 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/da >>> ta_approvals.html. >>> >>> >>> On Wed, Sep 28, 2016 at 2:12 AM, Nayeem Al Mifthah <[email protected]> >>> 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: [email protected] >>>> Cell:+8801914030574 >>>> Skype: nayeem.a.m >>>> >>>> _______________________________________________ >>>> Mailing list: https://launchpad.net/~dhis2-users >>>> Post to : [email protected] >>>> 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/> >>> >> >> > -- Jim Grace Core developer, DHIS 2 HISP US Inc. http://www.dhis2.org <https://www.dhis2.org/>
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
