Hi all. Just wanted to ask for any insight others may have discovered for dealing with errors that prevent submission of data rows.
Here is a simple scenario. An Enum column with a list of all values. Using a Valid_If expression, when a user is in one location a certain subset of values is shown. Users in other locations see a different list of values.
One of the values in the Valid_If was typo'd and didn't match the value inserted into the column definition. When a user chose this incorrectly spelled value and attempted to Save the row, an error occurred and row failed to submit.
The app was changed and redeployed but attempts to re-submit the row didn't work. Placing the app in Recovery Mode made no difference. The only solution we found that would work was to perform a "Reset Changes" and then have the user re-enter the row.
My question: Is there some way to recover from this error that does not require resetting changes and re-inserting the data?
I have dealt with this for years now and we always need to reset and re-insert. It just seems so unnecessary for such a simple problem. However, I would swear that I have seen posts from others that implied they were able to push through such an error. Is there some trick I've been missing?
Some years ago, 1 or 2 BG -Before Google- I remember AppSheet allowed saving unsynced values to JSON but now it appears to be gone.
This?
User | Count |
---|---|
28 | |
13 | |
3 | |
3 | |
3 |