Skip to content
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

Anomaly in vaccination events data when edited from multiple stores #4900

Open
nishaDangol-Sussol opened this issue Aug 19, 2022 · 0 comments
Labels
Bug: development Bug was found and believed to only be in development branches needs discussion

Comments

@nishaDangol-Sussol
Copy link

Describe the bug

It turns out that when you try to edit the vaccine event's extra information from multiple stores simultaneously, the store which syncs at last updates the server data with its data set discarding the previous changes made by other store.
For example, from Store1, edit the ID number from 001 to 111 and sync. From Store2, (don't manual sync)just lookup that patient, see it's ID number still 001 and change any other field value, like Ethnicity to Others and save. Now, sync from Store2. Now after all syncing, you'll notice the ID number as 001 and Ethnicity 'Others' (regardless of change made from Store1 simply because it wasn't the store to sync last!)

To reproduce

Steps to reproduce the behaviour:
as above

Expected behaviour

@sworup , decide if editing vaccination details should be disabled at all, except from homestore?

Proposed Solution

Leave if you don't know how to fix/implement. Edit this issue description and explain here if you know the best path of implementing the fix within the codebase.

Version and device info

  • App version: the latest apk

Additional context

Add any other context about the problem here.

@nishaDangol-Sussol nishaDangol-Sussol added Bug: ???? Placeholder; replace with 'development' or 'production' needs discussion labels Aug 19, 2022
@sworup sworup added Bug: development Bug was found and believed to only be in development branches and removed Bug: ???? Placeholder; replace with 'development' or 'production' labels Jan 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug: development Bug was found and believed to only be in development branches needs discussion
Projects
None yet
Development

No branches or pull requests

2 participants