Saving records that shouldn't be saved

I have app where in primary view user is searching through database via api.

  1. User is giving app a value to check, the bot is working and it gives back values about company name and address.(this is primary view)

  1. After that there is a action that by link to form transfer values to another view:

  1. in reference view the user chooses 1 button from 2(there are many validations) and this record can be put into the database unless there is already a record in the database with the same value, and here is the problem: the app/validations doesn’t let the user to save the record so he/she closes app with button checked, without saving the record so that is okey, but when he opens the app another time this record is saved and I don’t know why and how to fix it.

I’d guess you have Sync on start enabled?

If so, I’d expect this is involved somehow. I’ve never encountered your situation, where the app resumes an unsubmitted form. @AleksiAlkio , have you?

Disabled

It is happening while user opens app on another occasion.
At this point saving is impossible so I’m closing the app in desktop view.

I’m closing tab with buttons marked.

But when I open app in desktop view once more and put another number to check and I click on ‘Sprawdź’-save, this is the exact moment when the previous record is saved.

Had you saved the changes and re-synced after disabling Sync on start? If no, please do so.

Are you experiencing the same bad behavior when using the app on a mobile device? Is the problem only there in desktop mode? If only in desktop mode, this is likely a bug with desktop mode and you’ll need to contact AppSheet Support to report it. In that case, you should expect the bug won’t be fixed quickly.

actually, enabling sync on start somehow helped but not resolving the issue, because, while lauching app on the second time after row cauldn’t be saved, enabling this option causes this view at the start:

when user would click discard(odrzuć) the app would work fine but can I somehow automize this?

I’m afraid not.

To work around this bug, you could consider adding a hidden column that contains an indicator that the form is complete and/or valid, then setup a bot that deletes added rows that are not marked complete/valid.

Not sure if I totally understand your process, but could this be a timing issue? Like the API call is not executed yet when the validation is checked?

1 Like