Error: A value must be provided for item

[Anonymous]

I am building a flow that creates a copy of an item in one List to another List (on a different site). I have done this with one site successfully and can not find a difference between the two flows in any way, shape, or form; however for one of them, I am receiving the below error: 

"status": 400,
"message": "A value must be provided for item.\r\nclientRequestId: e489a373-f963-47a6-adc6-4bcf41fd2c36",
"source": "sharepointonlineconnectionprovider-westus.tip0-westus.p.azurewebsites.net"

The Flow to the left is the one that fails. Other than the organization of the columns within the list, these two lists and sites are identical (apart from names of course). 

Has anyone encountered this issue before/ knows what this error is or how to fix it? 

Thank you!

[Anonymous]

Same case for me. The solution works but it definietly will become more trouble the more complex the Flow gets.

[EnergiserFlow]

I have been having this issue myself and was able to find the solution. Deleting the create item action did nothing for me.

The issue I was having was that the column types weren't matching (in SharePoint).

List 1 expected the columns to be 'Lookup', and I was bringing columns across from List 2 that were 'Single line text'. The error message was being caused as List 1 was expecting more data in the form of a lookup. After altering the column make-up in List 2 (and updating it to actually be a lookup column) my flows began to work. 

Hope this helps!  

[Anonymous]

Hi All,

i not using any deleting action but still getting same error 

i am just inserting from excel to SQL table, when it trying to insert getting same error.

Can you help me what might be the issue.

[Basic_User007]

Also receiving this error message on create item for SharePoint within a flow - which was working previously but now not. The only change was turning the flow on and off...…...…. deleting the action and reading it the action did not resolve the issue!

[Eraser]

I had the exact same error when when trying to add a row to an Excel file.  The error was caused by using a special character in the column header.  The error would occur if I used "Case #".  Once I changed it to "Case No" the error went away immediately. 

I noticed the original poster had this column that had the # sign on the list that wasn't working, but the list that was working did not.

I suspect removing the # sign would also fix the problem here as well.  Knowing this I plan to avoid using any special characters in my column names going forward.

[teespolyglot]

Thanks, special characters turned out to be my issue too.

Just having a colon ":" or full stop "." in my column headers was causing the flow to fail. I looked at the output from the file writing automatically to Excel from my form and realised it used coding to replace the characters in the headers, which I hadn't when I typed out the column headers in the Row { "xxx": "dynamicinput",} input field.

e.g. try replacing colon with "_x003a_" and full stop with "_x002e_"

There are other codes you will likely need to look up to replace. Replacing these in about 10 of my columns saved me having to delete and re-input the flow for over 40 columns.

[ahalkela]

wt u did here when you removed and created the action again is creating the connection again.

your issue was that the connection was not created correctly. as a result, the action wihch is called did not show the full set of parameters which should be passed to the action. as a result, you got the error which is :

a value must be provided

[Ramadurai]

I am getting the below issue when I add Multiselection choice field in Add a new row to excel.

[ahalkela]

kindly remove the connection and create it again. or remove the action and create it again to form a new connection.

[Ramadurai]

Thanks for your response.
No luck 😶. I have also created a new flow and tried.
If I try without Mutiselection choice filed it works.

[ahalkela]

Well

This is an apim api call. 

Can u check the api which u r calling in this connector... Pass the values which u wanna use in the design time and see if it works via direct call or failing as well. 

[sonam29]

This actually worked for me. Thank you!

[Naeem]

I Was Also Facing The Same Issue But Nothing Worked For Me.
So I've Found That in Excel Fields Name Dot Operator Is Used in Dates So I've Just Replaced The Dot With Underscore & It Worked For Me. 🙂

[izzydudu99]

I resolved the problem by removing a dot and a forward slash in column names in the JSON of the Row property of the action "Add a row into a table".