Locking dataset after specific period

[Cnote (Arinze Okafor)]

@Cnote

after the migration to version 2.42.0, i noticed that all my datasets are automatically open for data entry despite the fact that i have lock exception set on all the dateset to prevent data entry, Now all dataset and period are opened by default for data entry, even after implementing the lock exceptions yet the data set still remain open, even data entered in 2019 are now opened and can edit by data entry user.

Please i will be glad if you could assist with useful guide on how to resolve this challenge.

Thanks @eyeseetea @Gassim @DHIS2-Community hello, Please can you assist me with any idea on how to resolve this.

after the migration to version 2.42.0, i noticed that all my datasets are automatically open for data entry despite the fact that i have lock exception set on all the dateset to prevent data entry, Now all dataset and period are opened by default for data entry, even after implementing the lock exceptions yet the data set still remain open, even data entered in 2019 are now opened and can edit by data entry user.

Please i will be glad if you could assist with useful guide on how to resolve this challenge.

Thanks

After migrating to version 2.42.0, i noticed that all my datasets are automatically open for data entry despite the fact that i have lock exception set on all the dateset to prevent data entry, Now all dataset and period are opened by default for data entry, even after implementing the lock exceptions yet the data set still remain open, even data entered in 2019 are now opened and can edit by data entry user.

Please i will be glad if you could assist with useful guide on how to resolve this challenge.

Thanks

Hello @eyeseetea @Gassim @DHIS2-Community please you suggest any idea on how i can resolve this

After migrating to version 2.42.0, i noticed that all my datasets are automatically open for data entry despite the fact that i have lock exception set on all the dateset to prevent data entry, Now all dataset and period are opened by default for data entry, even after implementing the lock exceptions yet the data set still remain open, even data entered in 2019 are now opened and can edit by data entry user.

Please i will be glad if you could assist with useful guide on how to resolve this challenge.

Thanks

After migrating to version 2.42.0, i noticed that all my datasets are automatically open for data entry despite the fact that i have lock exception set on all the dateset to prevent data entry, Now all dataset and period are opened by default for data entry, even after implementing the lock exceptions yet the data set still remain open, even data entered in 2019 are now opened and can edit by data entry user.

Please i will be glad if you could assist with useful guide on how to resolve this challenge.

Thanks

[Cnote (Arinze Okafor)]

After migrating to version 2.42.0, i noticed that all my datasets are automatically open for data entry despite the fact that i have lock exception set on all the dateset to prevent data entry, Now all dataset and period are opened by default for data entry, even after implementing the lock exceptions yet the data set still remain open, even data entered in 2019 are now opened and can edit by data entry user.

Please i will be glad if you could assist with useful guide on how to resolve this challenge.

Thanks

[Gassim (AL-Gassim Sharaf Addin)]

Hi there!

May I ask what was the version you upgraded from? And before upgrading to version 2.42, did you make sure to follow the 2.40 upgrade notes?
Also, are you using the new Data Entry app or the legacy/deprecated one?

Finally, please make sure to check that the user is not a user with the authority F_EDIT_EXPIRED / ALL.

Thanks!

[Waheed (James Wani Longa Poijo)]

Hello Mr. @Cnote,
I hope you’re doing well. I’m not entirely sure about the exact issue you’re facing, but I suspect the problem might be related to the Lock Exception settings under Data Administration. If you could share a screenshot of the Lock Exception configuration, it would help us replicate the issue and check for any misconfigurations.

Thank you!

[Cnote (Arinze Okafor)]

@Gassim

May I ask what was the version you upgraded from? And before upgrading to version 2.42, did you make sure to follow the 2.40 upgrade notes?
Also, are you using the new Data Entry app or the legacy/deprecated one?

Finally,

Hello @Gassim Thanks for your response, we moved from Version 2.41 to 2.42

we are the the new data entry app NOT the legacy/depreciated one.

Lastly, the user is a superuser and i did NOT find the listed authority as part of the user authority under the authority section.

Thanks

[Cnote (Arinze Okafor)]

Hello @Waheed Welcome back from your leave, hope you have a nice time.

Please as requested, attached is the screent from the dataset page and lock exception page for your review.

Thanks