cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Read Only Error Setting SharePoint Multi-Person People Picker

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. 

 

Multi-person config.png

 

"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:

input data.png 

 

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:

column in library.png

 

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!

1 ACCEPTED SOLUTION

Accepted Solutions
v-bacao-msft
Community Support
Community Support

 

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:

8.PNG9.PNG

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

2 REPLIES 2
v-bacao-msft
Community Support
Community Support

 

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:

8.PNG9.PNG

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous
Not applicable

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.

Helpful resources

Announcements
MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

Power automate tips 768x460 v2.png

Restore a Deleted Flow

Did you know that you could restore a deleted flow? Check out this helpful article.

Microsoft Build 768x460.png

Microsoft Build is May 24-26. Have you registered yet?

Come together to explore latest innovations in code and application development—and gain insights from experts from around the world.

May UG Leader Call Carousel 768x460.png

What difference can a User Group make for you?

At the monthly call, connect with other leaders and find out how community makes your experience even better.

Users online (1,766)