Hello,
Having an issue that I can't find an answer for. I have an app that uses SubmitForm to a SharePoint list and sometimes multiple people are sending updates to the same record. Here are the steps taken:
- User A loads a record in the app
- User B loads a record in the app and saves changes before User A
- User A has stagnant data in the form so some fields that User B filled in, are blank in User A's form, so when submitting, those fields end up blank, wiping out the updates made by User A
- User A does NOT receive the expected error message of conflicts exist with changes on the server, please reload
The key part here is why does User A not get an error message on the conflict? Any ideas?
I'd actually prefer to get the error message. I could experiment with a refresh prior to submit and see if that wipes out the form updates or not but I find it odd that the error message isn't triggering.
Thanks!