Sudden problem with Patch on Choice and Lookup fields in modification

[CharlesPP]

Hello everyone,

I'm experiencing a recent problem with the Patch function in Power Apps concerning the modification of Choice and Lookup fields. This problem didn't occur before and happens even if I restore a previous version of the application. The error only occurs when editing records, not when creating new ones. No changes have been made to the configuration of the corresponding SharePoint Online lists.

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

Here's an extract of the code that generates the error :

Patch(
    'Echeances List',
    currentEcheance,
    {
        // ...
        StatutApprobation: { Value: "En attente" },
        Tranche: { Id: cardTranche_1.Selected.ID, Value: cardTranche_1.Selected.Tranche }
        // ...
    }
);

Do you have any ideas on the possible cause of this sudden change in behavior, or on potential solutions?

Thank you very much for your help and advice.

Charles

[Yobeekster]

Fantastic, thanks for the guidance! However, I'm not sure there is a difference. The published authoring version, would show in the session details as in this case "Power Apps 3.23114.17". That is the published authoring version. I have looked at another app with an older published authoring version, and it shows in that case "Power Apps 3.23105.8".

Perhaps the issue is that end users need to refresh (F5) the web browser to get the latest published version, presuming that the latest published version from the developer is a stable authoring version. 

Please note that it can take about 30 minutes or more for end users to receive the latest published version from the developer. One of our apps is quite extensive, and it takes that long!

[Aria77]

Hello everyone. I've encountered the same issue. The type of column that occurred is 'User Type'. Additionally, I'm not using Patch within the powerapps. I've noticed that this error consistently happens only when clearing the web cache. However, upon refreshing the form, I can edit and save again. Nevertheless, it's inconvenient to do this every time. I've also tried changing versions, but none of these worked: "3.23121.9," "3.23114.19," "3.23113.20." Are there any other possible solutions available?

[yosefzav]

Hi there, was wondering if anyone had any new news on this subject. The powerapps team has prevented from setting the authoring version to 3.23105.18 and this has been causing problems the last few days since they forced the update off that version. None of the other versions seem to have a fix for this, not sure if other's are experiencing the same or have heard anything from microsoft about this

[Yobeekster]

Hello,

There is no issue on my end, whereas, I did have the same issue with Forms and/ or Patching as you did. Currently on 3.23114.19.

Please try a different browser, and also ensure that the issue is not a syntax issue. The syntax got me a few times, where it was my fault and not Powerapps.

I can assure you that the app I use is quite extensive with many Forms and/ or Patching scenarios, and they appear to all be working correctly. 

Hope this helps a little!

Are you able to post a screen shot of your code and a screen shot of your list details?

[yosefzav]

@Yobeekster unfortunately my code is very long for a screenshot, but the reason I don't believe is the code is because for my users if they go to the app in the browser for the first time and try to submit then they will get the error, but then if they refresh the webpage and submit, then the submitform will work correctly, even though nothing is changing between the two submissions.

I can recreate this too myself by logging in on a new browser, or in incognito mode, it always happens where if I refresh then it will work, even if the data is exactly the same or not changed at all. To me that sounds like something to do as an issue with the authoring version and the powerapp's version. After refreshing they will be able to use the form as normal for a bit, but if they close and come back in a future session the same will happen, an error that is then fixed for the time being by refreshing the webpage.

This issue really only started occuring to me on the 5th which is when powerapps forced my app to 3.23113.20 release (and none of the other currently allowed selected releases work either, including the 3.23114.19 release as well, and going back to the 3.23105.18 release isn't a selectable option anymore).

[Yobeekster]

Got it! Does this issue only to do with Forms or Patching? Also, what region are you located (assuming your users are in the same region), ie North America, Europe?

[yosefzav]

Both you could say, I have the Form run a SubmitForm, and then on the OnSuccess of the form there are a couple of patching formulas that run due to some logic that can only be calculated at that point. None of my code has changed between the updates. There are a few patches, but they follow this same layout:

Patch('DATASOURCE',varFormLastSubmit,{'QUESTION1': {Value:"Yes"}}, {'QUESTION2':varAnswer});

with varFormLastSubmit being set earlier as Set(varFormLastSubmit,Form.LastSubmit);

The thing is these have been working perfectly fine in the last update, but suddenly after the change it started throwing the errors. Here are the errors that it throws me (one taken from the form onfailure and the other from the app onerror):

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

I read on another forum post that it is important to exclude read-only columns from patches, but I have never tried to edit a read only column such as created/modified/etc, and it wouldn't explain why it was working on the older authoring version either. My patches in the OnSuccess only ever patch about 2 columns, and they are very specific ones that don't have to do with any read-only columns in sharepoint

[Yobeekster]

Got It! I have had those errors as well in the past. I agree with you regarding the reliability of the code before an authoring version change, but there actually might be a change that has exposed something that previously was allowed. 

Have you isolated the actual offending columns ? What I have had to do in the past with that issue, whether it is a Form or Patch, is to delete fields (Form) or comment out fields (Patch), until I have a successful submission, then reintroduce fields until it fails. Then when the offending columns have been identified, is to double check that the syntax is correct to any new standard that might be published. This should not take long. Instead of using the same form, copy that form and use that copied form as your test form for editing/ deleting/ reintroducing.

From my vantage point, the current authoring version is working, so its hard for me to look at that as the issue. Even though the code worked for you in past. I would go through the above exercise, if only to eliminate that as a possibility.

Also, if this is causing an issue for you as a business, I would summit a SEV A Ticket with PowerApps. This is the highest level severity, and they will work on it till it is solved. I would use this sparingly and only for emergency. SEV B is less severe issue, and they will respond during business hours. SEV A is around the clock.

Support | Microsoft Power Apps

Use "Included with your Power Apps paid license."

Fill in the appropriate information.

I have used SEV A and SEV B before and was quite impressed with their responsiveness. 

[ColonelDXB1]

3.23121.16 still giving same error. Absolutely amazed that this has been going on for so long. It's really damaging people's perception of being able to use PowerApps apps as a serious / viable business solution 😞

[lcordov2]

I reverted back to 3.23121.16 and it worked temporarily for a couple users, but now more users are reporting they are receiving the "patch" error. 

For long time power app devs, how frequent does this happen?  Luckily we are only starting to pilot this power app with a small subset of users, but am very concerned on pushing this out to the entire organization if it can randomly break like this.