-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicate identifiers assigned to beneficiaries. #594
Comments
@Gojo-Taqi why does the user have identifiers that are overlapping?
Important to remember that you don't have overlapping ids in rows of identifier_user_assignment. Use below query to figure out problems
|
Primary issue to be fixed through avniproject/avni-webapp#1022 . Closing this card. |
If you check, you can see the type IDs are different for both. |
@Gojo-Taqi can you check if catchment was changed for any of the subject that has duplicate identifier from subject_migration table? Asking since this results in duplicate identifier. |
There are instances of the same id given to consecutive individuals. Looking at code, it looks like this if condition is not required - https://github.com/avniproject/avni-client/blob/master/packages/openchs-android/src/service/IdentifierAssignmentService.js#L69 If we remove it, any errors will be flagged right away instead of getting buried in. This can potentially cause some failures on the Android app, but will ensure that id assignments are not duplicated. |
@vinayvenu duplicate of avniproject/avni-client#1092. Have added the details in the ticket. |
Describe the bug
In "Ctrith IPH" org, there are 6 individuals who duplicate identifiers assigned.
Run the below script to verify.
The folks from IPH claim that the users only use mobile application.
And on checking the sync telemetry for the user who created these beneficiaries, turns out that he has been using only one device so far.
And there is no way right now to verify whether the data was entered using DEA.
The text was updated successfully, but these errors were encountered: