Answered

Patch error: The specified column is read-only and can't be modified

(3) Share

Report

Posted on by biterbit

408

I have two apps that were recently updated using Power Apps Studio release 3.23113 and, since those releases, half of my users (about 70 people) have experienced errors when patching records: Network error when using Patch function: The specified column is read-only and can't be modified. The columns referenced in the error are two Choice columns in a SharePoint list. The columns have not changed in two years.

I am unable to reproduce the error in either the Studio or production environments.

The only reliable way to stop these errors is for the users to log out of their 365 session and log in again. However, after about two weeks of managing these problems, I am now finding users getting the errors again for the second time.

I found this thread about a similar problem, but the proposed solution was to revert to an earlier Studio release. However, that option is not longer available as new releases have occurred. I have tried re-releasing the apps using newer Studio versions (up to 3.23121), but the errors continue.

In the earlier thread, the problem was described by @v-jefferni as 'a known issue'. If so, is there any news on when it will be solved as the support cost of managing many users with this intermittent issue is very high?

Categories:

Building Power Apps

I have the same question (0)

All responses (20)

Answers (1)

lcordov 47 on at

Like (0)

Report

The "workaround" of rolling back the authoring version is not an actual fix. Whenever I have tried it, the issue will seem to be corrected for a couple hours then resurfaces again. The lack of communication from Microsoft regarding this issue is very disappointing as it's becoming difficult to push for use of Power Apps in my organization with such a critical error.

Was this reply helpful? Yes No
SteveROPS 9 on at

Like (0)

Report

I'm having the same issue here with an app used for the last year across 250 sites. Since Monday users (at random it seems) get the patch error. Refreshing the browser or logging off and on seems to help, but that isn't great for the end users!
Done a bit of research and found some information that it might be to do with the edit form having some cards set to view. I've reset all of the cards to edit and then back, and have just published an updated version to see if it helps. Fingers crossed.

Was this reply helpful? Yes No
lcordov 47 on at

Like (0)

Report

Please let us know if this helped correct it!

Was this reply helpful? Yes No
biterbit 408 on at

Like (1)

Report

Thanks for the confirmation that it's not just me! I looked at the two apps which have been reporting errors. One has a form containing some View mode datacards, and one does not. So, at first glance, it does not appear to be a common factor. However, I look forward to hearing if your changes have any effect.

Was this reply helpful? Yes No
biterbit 408 on at

Like (0)

Report

I published a new version of another app today and I am now seeing the same errors on that. In this case, the control reporting the error contains a Patch statement but there is no underlying form. This would seem to make the form datacard theory less likely.

Was this reply helpful? Yes No
AlexanderAhenn 19 on at

Like (0)

Report

I have the same error. Changing my fields from "view" to "edit" did not solve the error

Was this reply helpful? Yes No
biterbit 408 on at

Like (0)

Report

I went to raise a support ticket with Microsoft today and, after entering the problem details, I was directed to a Known Issue record saying:
Workaround
The issue is a regression in the 3.23111+ authoring versions.
Republish your app to the latest version in the Power Apps Studio.
Frustratingly, it does not specify which (latest) version fixes the problem. The version I am currently using is 3.23121.20 and the latest one available to me is 3.23122.13. I will try releasing the app using the latest version and see if this fixes the issue.

Was this reply helpful? Yes No
AlexanderAhenn 19 on at

Like (0)

Report

I have tried all version available, and none helps with the issue

Was this reply helpful? Yes No
lcordov 47 on at

Like (0)

Report

Not sure why Microsoft keeps directing people to this workaround and considers it resolved. It's clearly not a fix and will the issue will resurface within hours.

Was this reply helpful? Yes No
lcordov 47 on at

Like (0)

Report

Were you able to release with the latest version and did it resolve the issue?

Was this reply helpful? Yes No