Tracker app - uniqueness check no longer works

Support - Assistance technique
1

Dear @dhis2-tracker team,

Yesterday, one of my users pointed that the Tracker app (DHIS2.40.4) stopped to check for uniqueness of the TEA during the clilent/customer registration. I remember it was working fine before.

image
image1280×105 10 KB

Interestingly this uniqueness check works on the new Capture app

image
image1280×203 26 KB

Would it be possible to check why it stopped to work?
Thank you.

Regards,
Ulanbek

1 Like
2

Hi @Ulanbek

Thanks for the screenshot and the helpful explanation. I’m, however, not able to reproduce this issue - please see screenshot below:

image
image1219×1016 55.8 KB

I have created a unique TEA “special” and tried to enter the value twice but when I pressed ‘save and add new’ or ‘save and continue’ it showed me a dialog that the value is a duplicate. The difference is that Capture app because it’s the newer app, it handles this in a much better way than Tracker Capture app by showing this message right after entry of the value whereas in the older app it only appears after completion of the form.

The TEA here is unique in entire system, but is yours unique to specific OU? Can you reproduce this on play? Thanks!

3

Hi @Gassim

That’s the problem as I cannot show how it used to be before :slight_smile: It seems that functionality gone forever. The main problem came up as I have first stage shown in the client registration page. Therefore the users first fill up the entire form, and then find out, if the client already exists… Although they were told to do search before. But this is human factor, so cannot control :frowning:

So would it be possible to address this issue to the developers?

Thank you

Regards,
Ulanbek

1 Like
4

Hi @Ulanbek

I understand your situation and thank you for the explanation. Maybe you could set warnings using program rules if the search is not used first? Or maybe lock all fields until the number is entered so that at least this will be a way to enforce the next step to search?

Currently, I don’t think there’s any development in the Tracker Capture app and the focus is on the newer Capture app, but I hope the program rules suggestion would help?

Thanks!

5

Hi @Gassim

I would be grateful if you can show how to check for uniqueness by the PR and prevent the next steps.

Thank you @Gassim

Regards,
Ulanbek

6

Hi @Ulanbek

Thanks!

Sorry, I didn’t mean to check for unique across the system / program using program rules because I don’t think that’s possible; however, I was addressing that the issue when data entry users don’t enter the unique number before the other fields.

The idea is to create a program rule with this condition ‘if the field for unique id is null’ then the action would be to close all the other fields so the first step the data entry user will have to make is enter the unique id. Does that help?

Thanks!