You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
to111
and sync. From Store2, (don't manual sync)just lookup that patient, see it's ID number still001
and change any other field value, like Ethnicity toOthers
and save. Now, sync from Store2. Now after all syncing, you'll notice the ID number as001
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
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: