You’re offline. This is a read only version of the page.
Hi!
I have a trouble with my flow. Im getting an error: Flow save failed with code 'WorkflowOperationParametersExtraParameter' and message 'The API operation does not contain a definition for parameter 'item/itemname.
So I want to use "Add a row into a table" function. I have composed table, and JSON code, Add row function recognizes my file well, but after setting all up im getting that error.
After removing this column ([Pierwotne/konsekwencje]), everything run smooth, but this column is kind important.
The weird thing is that I use everywhere "/" as separator, but in error "." is used.
Do you have any ideas?
JSON code fragments:
Add a row into table:
Error while I want to save:
I also met the same problem today, so when I was searching for solutions, it is your message remined me of the "/", then I deleted it, now it works! thank you！
PSA
As of 5/24/2024 bug is still active. Switching to old designer works as recommended.
@SamLed Very helpful tips. I follow same method while creating new columns in SharePoint list/libraries.
@Olut11 @lenap Here are few best practices for naming SharePoint columns:
You can find more information about best practices and how to find the correct internal name of your SharePoint list/library columns at: How to find the Internal name of columns in SharePoint Online?
Please click Accept as solution & 👍 if my answer helped you to solve your issue. This will help others to find the correct solution easily. If the answer was useful in other ways, please consider giving it 👍
Hi @Olut11,
Yes, I also don't use special characters in my column names, I also exclude spaces and accents.
Tip: I create the column without spaces nor special char and then rename it with them, this way the internal name of the column which is used by http requests (or Power Automate actions) is clean but users see a column name that is more natural to them.
If I have answered your question, please Accept the post as solution.
If you like my response, please Thumbs Up.
Yea, it is preety weird but changing to old designer worked.
Also I deleted the "/" in column name by script, beacuse I think it created some trouble.
Thank you!
Hi @Olut11,
Try switching to the old designer, the new one is quite new and I've already encountered unexpected issues that I haven't encountered before with already designed flows which I fixed by switching back to the old designer. I haven't delved into these issues yet as it works with the old one.
If I have answered your question, please Accept the post as solution.
If you like my response, please Thumbs Up.
#1
WarrenBelz
146,743
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
66,079
Most Valuable Professional
Share
Report
All responses (
Answers (
