Suddenly I cant update a column - I get an error it is read-only

(0) Share

Report

Posted on by brandolph86

Hello,

I have a process that does a patch to a table when a button is clicked. it updates two fields.

It worked two days ago. Today it does not. I get an error saying the field is read-only. I find no setting anywhere in Dataverse to show read only or not. we have not changed these fields at all in the table.

Error:

Network error when using Patch function: The specified column is read-only and can't be modified.

I found another environment where this code lives and it works there. No table changes have been made - code is all the same.

Why does it work on one environment and not on the other?

Thanks!

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (1)

CU22081303-0 150 on at

Like (1)

Report

If the code is all the same but it only works on one environment, my first suspect is security roles; make sure the user has been given a role with read & edit permissions for that table or is System Admin, especially if this is a custom table. Append and Append To roles will also be necessary if one of the fields is a lookup. Security roles can be added to solutions, but a deployment doesn't carry over who was given what role.

Another troubleshooting step would be to have the user try making the same changes manually through a model driven app form if possible. If they can do it there, then it shouldn't be a permissions issue.

It's also worth checking if you have any Business Rules that make a field read-only under certain conditions.

Was this reply helpful? Yes No
HenWang Microsoft Employee on at

Like (0)

Report

Hi @brandolph86 ,

Just by the way, can also try to create to create new column to check whether this is really specific column related issue.

Best Regards,
Hen Wang

Was this reply helpful? Yes No
Parashuram 6 on at

Like (0)

Report

There could be chances of this field might have configured in field security profile, pls do check.

Was this reply helpful? Yes No
Verified answer

brandolph86 27 on at

Like (3)

Report

First, Thanks to everyone who Replied. We did use your ideas to troubleshoot.

We think we found the culprit. At least, the change we made seems to have fixed the issue.

When I got in this morning, I heard from the Business Users that this was a problem in Production also. This code has definitely not been updated in several weeks and was working last week.

There is a "setting" in the app, under "upcoming features", named "Explicit Column Selection". This was turned off, so apparently, when we tried to do a patch, all the columns in the row were being updated in some way, including the ones that were "read-Only", but were NOT supposed to be patched.

We turned on the feature and the code worked as intended.

It seems Microsoft updated something last week around this feature that impacted my application. If not, maybe we learned something anyway.

Thanks for all your help!!!!

Was this reply helpful? Yes No