while I was trying to debug & reproduce the PouchX bug, I found two Issues related to PouchX and syncing data to CouchDB, it could be related to the reported bug.
Describe the bug
If you remove a patient who has multiple appointments e.g (8 appointments), you will notice two issues,
1- the deleted patient and related appointments won't sync to CouchDB until you click on the top right sync button.
2- after you click on sync button, you will notice not all the appointments will be removed from CouchDB, only 4 of the 8 will be removed, and 4 appointments will stay at CouchDB.
open (CouchDB/_utils) to see the changes in docs numbers, there should be 2 patients and 3 appointments
go back to apexo and delete "Sara Beam" who has two appointments.
check the numbers in CouchDB you will notice no changes until you click on re-sync button at the top right. (First Issue)
after re-sync go check the CouchDB you will notice only one appointment is removed, instead it should delete the two appointments of "Sara Beam" (Second Issue)
Desktop (please complete the following information):
OS: windows
Browser chrome 84.0.4147.105
Apexo Version [4.0.1]
CouchDB Version [3.1.0]
It could be related to reported bug at PouchX, if its not I will do my best to reproduce it after fixing this issue.
while I was trying to debug & reproduce the PouchX bug, I found two Issues related to PouchX and syncing data to CouchDB, it could be related to the reported bug.
Describe the bug If you remove a patient who has multiple appointments e.g (8 appointments), you will notice two issues,
1- the deleted patient and related appointments won't sync to CouchDB until you click on the top right sync button. 2- after you click on sync button, you will notice not all the appointments will be removed from CouchDB, only 4 of the 8 will be removed, and 4 appointments will stay at CouchDB.
To Reproduce Steps to reproduce the behavior:
Desktop (please complete the following information):
It could be related to reported bug at PouchX, if its not I will do my best to reproduce it after fixing this issue.