Read Only Error Setting SharePoint Multi-Person People Picker

[Anonymous]

It seems this changed over the last few years and I cannot seem to find a solution that works.  I have tried setting with formatted JSON via an array and I've tried just clicking the button to "switch to input entire array" and just setting the field but nothing works.  In both cases, I get errors that a field is set to read only.  I am using an Update Item SharePoint action and just trying to set a Person field that allows multiple values. 

"The 'input.paramteres' of workflow operation <action name> of type OpenApiConnection is not valid.  Error details: The API operation does not allow writing a value for parameter 'item/PeopleToNotifyOfRenewal[0]/Display Name'.  This parameter is read only."

The name of the field changed to Email if I tried to set that field.  This is the input data being used from that source multi-people picker being fed into the Update action:

 

I am using content types and site columns, the same site columns are added to the source (SP list) and the target (SP library).  Here is the site column in the target library that I am trying to update:

I am able to upload a file into the library and set that column via the OOTB modern properties just fine.  My flow goes like this:

1. Users fill out a SP modern list form, filling in properties and attaching files via list form attachment

2. Flow starts and does some if checks.  It gets all list attachments and saves them to a library and sets all the same column metadata

Ideas? Thanks!

[v-bacao-msft · Accepted solution]

HI @Anonymous ，

I can reproduce a similar issue here, but I am not sure if this is a bug.

As an alternative, you can first use the following methods to solve your current problems:

Best Regards,

[Anonymous]

That was it!  I had tried that same thing before, but I included Email in another line and had manually typed the claims prefix characters.  Appreciate the workaround.

[NakulSuryanC3]

Thank you. This works!

[jermMM]

The method accepted here as a solution indeed works! If you're seeing this, be aware that there is a more efficient approach.

This post illustrates an alternate solution: https://tomriha.com/how-to-select-specific-values-from-an-array-in-power-automate/

You can avoid the need for the variable/apply to each method by using 'Select' action to isolate 'Claims' values from the array.

I had built a flow using Initialize Variable>Apply to Each>Append to Array to copy items from one SP list to another. Both lists had several mulit-person fields and it took several minutes to run the flow. Following the post above, I revised the flow to use 'Select' and populated the select output to my Create and Update actions. Now the entire flow processes in seconds. Both faster and simpler, IMHO.