How do we prevent accidently modifiying the data in dataset/events/tracker

Support - Assistance technique
1

Greetings Community experts,

After we click complete, still we can go ahead and edit the data by dhis2 design right, is there anyway we can prevent that?

It’s causing lot of trouble in our projects because of accidental typos while seeing the entries they entered.

2

Hi @jthomas

I have been asking this question as well and proposed to create an ability to block the past year events or enrollments with certain rules or by user permissions, so no one can edit\amend anything. It is more like accountant program, where the event fixed, and not modifiable when the financial year is closed\locked.

Still waiting from tracker developers… :slight_smile:

1 Like
3

Hello @jthomas and @Ulanbek

There are a few ways you could consider locking the data.

For datasets -

  1. You could consider configuring the attribute expiry days if you want to set a limit of number of days before the data set is locked automatically
  2. You could configure data approval workflow if you want to make the data uneditable after approvals

For Events

  1. You could consider setting an expiry date value
  2. And also checking the Block entry form after completed checkbox

For Tracker
Consider these or a combination of these attributes -

  1. Completed events expiry days
  2. Expiry period types and expiry days
  3. To lock the entire TEI, maybe deactivating a TEI could work for your use case.

Please let us know how you get on. We would be interested to hear more about your specific case if these attributes (or their combination) do not meet your needs.

Best

1 Like
4

Hi @Rohit

Thank you for your solutions you proposed. My case is a bit complicated, therefore none of above is not suitable for me.
Here is the my use case:

  1. Users crates cases(events), which has descriptive, actions and result part.
  2. The case can last from 2-3 months for few years, until results achieved
  3. The case can be edited during the year, and then only certain users, such as coordinators or project managers can do amendments after
  4. The user must have an ability to see the case details, but not able to edit it
  5. The case cannot be completed until the result achieved.
  6. Even the event completed\expired there is some details may come up later, so it must be able to edited by the group of users\managers later.

In order to achieve these, I have tried to hide stages by the program rules, and give an access some group of users. I have tried to analyse event date, and compare the years with current one. The problem is if the stage has any data element with data cannot be hidden, therefore I hide program stage sections inside. It led to the another issue, when the user can change the date of event and get access to the case details and make amendments. Btw program rules will not react it you change the event date, so you can’t control if the event date has been changed or not.

Also we can’t deactivate the TEI, as it will affect the indicators and reports

These are reason why would be greta to create an ability to lock from editing TEI\Enrollment\Event with certain rules, and make them editable for some other groups

I believe @jthomas has different use case, and can share with us.

Thank you for your support Rohit.

Regards,
Ulanbek

1 Like
5

Dear @Rohit @Ulanbek I found atleast in the version i’m using (2.39.x) an option like below. Block entry form after complete. This is exactly the one i was looking for. Thank you so much for your feedbacks. it gives me good perspective for other scenarios.

image
image1068×496 16 KB

1 Like
6

Hi @Ulanbek
Apologies for the slow reply.

Perhaps we can speak to get more details about your scenario. If I understand correctly, you are looking for the ability for different user groups to have different access rights for different sections of the same event?

Best,