Answered

Network error when using Patch function

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hi everyone,

Following 40 or so successful form submissions to a SharePoint list, one of our end users experienced a case where the app permitted him to save the form entries with no data - even though the controls were validated against this. The problem was extraordinary in that subsequent attempts to update the form were not met with success. That ended up with me adding the missing data for him on my account (different browser instance.)

Checking on the app now, when the app is launched on a new instance, it seems to throw up the patch error. Initially it allows me to save data even with no data added. If I try a second time to save the app form without any data, the validation works and the app fails to save until I have added data. The Network error appears at the top of the app.

Only when I reload the app in the browser does the app continue to work with no further issue.

Wouldn't this issue be resolved by having the option to automatically load the app twice on startup?

Categories:

Building Power Apps

All responses (2)

Answers (1)

Sort by

Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

The irony is that the only patch function I have added to one of the Form buttons has not been published. Therefore why would the Patch error materialise?
Verified answer

Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

I think I can see what's going on with this. If data changes are made to the same records, in quick succession, the Power Platform struggles to make the adjustments over the network, at the pace the user is attempting to set. I found that I can mitigate this by adding validations (i.e. required information) at the app level.

Previously I had only set validations on SharePoint. When I tested this by applying quick data entries at the app, Power Apps appears to get confused and can't maintain pace on the network with the changes (my judgment on this is based on the observation that the app begins to allow form submissions with neither data added nor validation.) Having tested validation at the app alone furthermore, seems to screw with the overall validation. I therefore, recommend validation be applied at both the app and SharePoint levels and that up to 1 minute intervals between form submissions be allowed to elapse. I should be interested to hear others' take on this.