Hi, sometime when I get an error on my app and after I solve it, still can not sync again. I have to click option on my app and clear storage data that deletes the app and then have to install it via its url again.
Is there a step to solve the stuck rows without having to clear storage. Thanks.
Solved! Go to Solution.
When an Appsheet data row causes an error that prevents submission of that row to the servers, there is a "Reset Changes" menu option that appears in the side menu of the app. Tapping that menu option will clear the current LIST of unsubmitted rows preventing further errors. Then just ensure that the app has be updated to the correct version that addresses the fix. Once verified, resubmit the affected rows(s).
IMPORTANT: When an error does occur, the user is allowed to still work in the app attempting to submit additional adds and edits. HOWEVER, these additional submissions will stack up BEHIND the row in error. Tapping the "Reset Changes" button will permanently delete ALL unsubmitted rows - even those that did not encounter an error - and all unsubmitted rows would need to be reapplied once the fix is deployed successfully. This can be an issue if a user is not aware of the error (in some app configurations they will not see an error is occurring) and they continue to submit additional changes. A user could be using the app for days without any idea there is a problem and potentially have hundreds of unsubmitted changes. Therefore, it is important to monitor closely for any errors in the Audit Logs and react quickly for any critical use apps.
There are specific rows are causing issues, manually remove and re-add them via the app or directly in the data source
When an Appsheet data row causes an error that prevents submission of that row to the servers, there is a "Reset Changes" menu option that appears in the side menu of the app. Tapping that menu option will clear the current LIST of unsubmitted rows preventing further errors. Then just ensure that the app has be updated to the correct version that addresses the fix. Once verified, resubmit the affected rows(s).
IMPORTANT: When an error does occur, the user is allowed to still work in the app attempting to submit additional adds and edits. HOWEVER, these additional submissions will stack up BEHIND the row in error. Tapping the "Reset Changes" button will permanently delete ALL unsubmitted rows - even those that did not encounter an error - and all unsubmitted rows would need to be reapplied once the fix is deployed successfully. This can be an issue if a user is not aware of the error (in some app configurations they will not see an error is occurring) and they continue to submit additional changes. A user could be using the app for days without any idea there is a problem and potentially have hundreds of unsubmitted changes. Therefore, it is important to monitor closely for any errors in the Audit Logs and react quickly for any critical use apps.
where to access Reset Changes
In will show up in the side Menu of the app ONLY when there is an error that prevents 1 or more row from being submitted.
Thank you very much. Yes I've tested it out and found that button.
I have other question plz, when sending the data as recovery option it only opens with google doc file so is it possible I send the recovery to google sheet file.
No, I am not aware of any ability to control hoe the recovery files are created.
User | Count |
---|---|
15 | |
11 | |
10 | |
8 | |
3 |