cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
trishmalloy
Post Partisan
Post Partisan

The 'inputs.parameters' of workflow operation 'Create_item' of type 'OpenApiConnection' is not valid. Error details: The API operation does not allow writing a value for parameter 'item/Clery_x0020_Training_x002f_Educa[0]/Id'. This parameter is read only.

Hello,

 

I'm confused by this error message, "The 'inputs.parameters' of workflow operation 'Create_item' of type 'OpenApiConnection' is not valid. Error details: The API operation does not allow writing a value for parameter 'item/Clery_x0020_Training_x002f_Educa[0]/Id'. This parameter is read only."

 

Why are the second entries created this way?

 

What is the fix? Why is this happening? I'm creating a flow to copy a SP list item to another list and add attachment if it exists to another list in another site collection.

 

Example.PNG

10 REPLIES 10
rocamp
Community Support
Community Support

Hi @trishmalloy ,

 

My first suggestion would be to confirm that this field is not set to read-only. Try setting up a separate, simple Flow that updates this field and see if the error still occurs. If not, then we know the issue is isolated to this specific Flow. If so, then we know it is something related to the field.

 

This can also happen if you have a process trying to write to the same field in parallel. So, confirm you are not doing that.

forcedLightning
Advocate I
Advocate I

I've run into this same issue, and the field is not read only.

bobbyblue
Regular Visitor

I also am experiencing this issue.  In my situation, I am copying a list to another list, and the issue occurs with a multiple choice field.  I'm guessing, but I think it's saying that while you can submit the value, it doesn't also want the ID number.

 

"ID": 1,

bobbyblue_0-1605073965757.png

I am interested in the answer though!

TFalconer
Helper I
Helper I

@rocamp 
I am also having this issue today. Has anybody had any luck with finding a solution? Mine is also a multi-choice field. I actually don't want to change the data at all, I want to leave it the same but when I select the dynamic content this is the error I get too. The field is not read only.

Karin-K
Regular Visitor

I have also run into this error, but I am not trying to create a new list item. I am simply trying to update three fields in an existing item and because my multi-selection field is required, Power Automate forces me to include a value there. I try to maintain the existing value and I get this error that I cannot update the field. I do not want to update the field. It seems my only recourse is to go through the effort to parse the field so I can maintain the values that are already there or else I have to make these fields not required so I can leave them out when I update the fields I want to update. I swear this used to work previously. It's bad enough that I have to update fields that aren't changing when I use a SharePoint Update Item action. Now I have to go through a huge number of steps just to keep the data unchanged so that I can update an item in the list. This is not acceptable.

JQuast
Regular Visitor

Hi, 

Take a look at this article. Use this to setup a claims array for the multi person or group field and use the output of Select to update existing or new items. I got same error using OOB field, but this method worked. When updating multi person group field, you need to change it so the input takes array. 
Power Automate – How to update Single or MultiPerson field in SharePoint | Knowledge Share (spknowle...

rcouture
Frequent Visitor

Although an earlier post, I found a solution here (translated to English):

https://lodesharepoint.com/power-automate-input-parameters-error-id-readonly

 

You need to parse the multi-select column, add just the value elements to an array variable and use that variable in your dynamic selection for the field.

clengcleng
Regular Visitor

hi! i also encountered the same error. i already did the parse json but the same error is encountered.

did someone resolve the issue already?

thank you.

Toresing
Microsoft
Microsoft

I came across a similar issue. I ended up combining tips from two articles to solve it

I started with the first which worked for a choice field. I had to modify the steps in the first by substituting "Claims" for "Value" in the Apply to each step. I got that explanation from the second article.

Using the first article worked for me once I made sure I had formatted everything. I have to agree with @Karin-K  this is really annoying to need to create this workaround.

Helpful resources

Announcements
Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

New Ideas Forum MPA.jpg

A new place to submit your Ideas for Power Automate

Announcing a new way to share your feedback with the Power Automate Team.

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.

365 EduCon 768x460.png

Microsoft 365 EduCon

Join us for two optional days of workshops and a 3-day conference, you can choose from over 130 sessions in multiple tracks and 25 workshops.

Users online (1,961)