Our warehouse personnel create each of the above rows and selects unloading as complete. We then change the verification status from pending to complete. For the past month, after I change the value to complete, the next day, some of the rows are reset to pending. What could be the issue?
Is it a straight forward EnumList? or is it a calculated field? How many devices and users are operating the App?
EnumList with an initial value and also an edit if condition. The intial entry is made by a seperate user(used in 1 device) and the verification status change is made by another user(used in 3 devices).
Hi @Gokul1
Can you check:
1) expression is in "initial value" and not in "formula"
2) you didn't check the option "reset on edit"
yes! its in the initial value column and reset is on edit is not checked. it was working fine for a year. im facing this issue recently
@Gokul1 wrote:
Our warehouse personnel
This, added to:
@Gokul1 wrote:
the next day, some of the rows are reset to pending.
makes me suspect a syncing conflict.
let's say:
- user1 is connected, user2 is offline
- user1 updates the row to "complete", while user2 is still offline => database set the [Verification] to "complete"
- user2 changes a value from this record, let's say [bags number] change from 31 to 32. For this user, [Verification] is still to "pending".
- user2 gets back from offline to online. The syncing process starts, and will replace the [Verification] status to "Pending", at the same time as [bags number] is being updated. This is because syncing does not occur on specific values, but on entire row.
Would that assumption match the real-case situation?
If you have a doubt, I would suggest to investigate using the audit log feature:
this seems like a plausible scenario, but the verification status is seen as complete for a whole day in all devices and then it switches to pending the next morning. Im looking at the audit logs..lets see
If you are using Google Sheets, check the Cell history when the status change happened. That could give you more ideas for the reason.
User | Count |
---|---|
43 | |
26 | |
23 | |
14 | |
13 |