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

[LeeKengLeong]

Hi there, can I check if the patch problem has been solved yet? I am still using the previous authoring version 3.23105.18, and noted that the latest authoring version continues to produce an error when you try to edit the form. Thanks!

[LeeKengLeong]

Hi there,

Really appreciate your sharing that Authoring version 3.23105.18 still works fine. Can I ask if there is an updated authoring version that has resolved this patching error? Thanks!

[Yobeekster]

There is a new recommended version 3.23113.20, and  have tested it with success. It patches to lookup columns and it also patches using the ShowColumns(), as it is supposed to. 

Please post if this works for you to. Thanks!

***Update: It also appears that Choice columns work too.

[ozhally]

Hellos.

I published with version 3.23113.20 on Thursday (30/Nov/23) and started having read-only column issues reported by end users (SharePoint data backend).
I have rolled back to 3.23105.18 and the issue appears resolved.

I am in Queensland, Australia.

[LeeKengLeong]

Hi ozhally, really appreciate your sharing. 

Power Apps setting does not allow me to roll back to 3.23105.18 now. Instead, I only have a choice of 3.23113.20 or the later version at 3.23114.7. 

Can I ask if you know if authoring version 3.23114.7 is stable? Thanks!

[ColonelDXB1]

Having this issue again!!!!

Have tried authoring versions 3.23114.19 and 3.23121.9 - both having the same issue, unable to patch a sharepoint column.

Come on PowerApps Team!!! This was a known issue before for a LOT of people... How did you let this slip into yet another authoring version again!!!!

[bt90]

a combination of updating the app authoring version to 3.23113.20, and windows-webplayer version to 3.23113.15 might resolve the issue

[Yobeekster]

Hi Colonel (Sir👨‍🌾),

I can confirm that Patching works on LookUp and Text columns while also using ShowColumns(), on version 3.23114.19.

I have been monitoring this closely, and like you it is a loss of confidence, not knowing if/when this issue will creep in again. These are basic working elements that have been reliable before and should never be in question as to their reliability, but unfortunately they are now. 
The main issue I have is that there has not been a response that I am aware of from Powerapps specifically addressing this issue as it is not a trivial issue. This is about basic things failing, which is quite concerning. 

[Yobeekster]

Hi bt90, 

Thanks for this suggestion, could you kindly describe how to do update  "windows-webplayer version to 3.23113.15"?

Thank you!

[bt90]

check the session details under settings while the app is open, the last line that starts with "Power Apps" will tell you the webplayer version. I'm not sure of a good way to force the webplayer to update, but each user's webplayer version is completely separate from the app's authoring version. If I check my app's usage analytics for 12/4/23 I see my userbase split between webplayer 3.23113 and webplayer 3.23105, and the users on 3.23113 are able to run the patch function without any errors.