Multiple Editors Error

[Mattw112IG]

I have an app and it will have multiple people using it all the time.

SharePoint Lists for backend.

Collections for the galleries, but edit forms tied to SP List.

Today I noticed that if User a edits a record and saves, then user b edits that record (without refreshing the app) then when they try to save it just doesn't do anything.  No error and doesn't update.

How do I make it so there's always fresh records when someone edits it?  Add a bunch of refreshes in front of every on select, on submit, on change, ...

Or is there easier way?

Thanks,

Terry

[WarrenBelz]

Hi @Mattw112IG ,

The user needs the current version of the record to use a SubmitForm. It is strange that they are not getting the "big read message" of a mismatch as my users do (and then hit the refresh button, put their changes back in and re-save).

Using a Patch or UpdateIf statement instead of SubmitForm may alleviate this.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[v-siky-msft]

Hi @Mattw112IG ,

If multiple users operator on one SharePoint list at the same time, there should be an ETAG mismatch error.

As you said if you want to solve this problem, you have to refresh the data source.

Could you try to add a refresh function before the submit function and check if the issue is gone?

Refresh('SP list');SubmitForm(Form1)

Hope this helps.

Sik

[WarrenBelz]

Hi @Mattw112IG ,

I did not suggest the refresh mentioned by @v-siky-msft as I was concerned about the user losing their input when the data source (and form) was refreshed before the submit. The "big red message" is the ETAG mismatch error mentioned below.

You might try both - happy to elaborate on mine if required.

[Mattw112IG]

So if I did a refresh on a SP List right before I submit form, that would lose the inputs in the edit form?

Terry

[WarrenBelz]

Hi @Mattw112IG ,

Please test this - I have not done it (sorry not on PC presently) but logically when you refresh a data source and a form is based on this, the form will refresh to the current state of the record (which is not yet saved).

I can tell you however that with what you are experiencing, a Patch/UpdateIf should do the job. It is strange however that the user writing the second record does not get the error as my users experience this regularly do a refresh (actually go back to the gallery and re-select) , reinput and save.