-
Notifications
You must be signed in to change notification settings - Fork 26
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 EAS records created during sync for organisation that uses both approvals and media in encounter #678
Comments
…ual_id is same as entity_id for Subject entity type.
What to test
|
…load has been done.
The server change looks non-backwards compatible. Won't this prevent sync for those who are on an older apk? |
If there are older implementations, there will be duplicates in the client that won't be available in the server. Need to test that this doesn't cause any issues on the client. In any case, we are still going ahead with this change. |
Still we get the duplicate entries attached the video for the references af8b9ecc-bd6e-4122-bad0-85f8e50e61d7.mp4 |
The query used is incorrect because it is not checking whether the status is approved or pending. The two entries in are in two different status - which is allowed. We do not overwrite the previous entry. |
…load has been done.
…ni-server#678 (cherry picked from commit e9e09a7)
Reproduce
The text was updated successfully, but these errors were encountered: