Preventing users from overwriting each other's changes?

AppSheet AppSheet Q&A
, , , ,
1

I have a rather large app that has a growing pool of users. An issue I’m beginning to see is that we now have a sufficient number of users that on rare occasions, one person is “blowing out” another person’s changes because they are editing the same record either at the same time, or in quick succession so that a sync is not happening in between and old data from one user’s “copy” of the data is overwriting another user’s changes.

Is Quick sync a good possible solution for this? Any other suggestions on how to prevent this? I already have automatic updates on. I do have a spreadsheet formula on one of the tables the app uses, and that contraindicates using quick sync, but it doesn’t change often, so not sure how big of a “risk” that poses.

Any suggestions are welcome. Thanks!

1 Like
2

So if I remember correctly, all of the user’s data changes are written to the source, AppSheet writes them in the order it receives them. So the most recent change should always be reflected (there might be caveats to this with “offline users” who only sync when connected).

If multiple users are editing the same data fields, I’m afraid I don’t have any good suggestions from an AppSheet perspective. Trying to lock users out of editability on the fly like that is likely to cause more frustration and confusion than it is worth.

Is it possible to coach/train the users or divvy up the work so users aren’t working in the same row of data at the same time?