cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
krishnabnv
Microsoft
Microsoft

Microsoft Flow input parameters maximum length -1 error

We are facing an error on maximum length '-1' limitation when we a SQL Stored Procedure in triggered from PowerApps button click in Microsoft flow.
Below is the error
"The 'inputs.parameters' of workflow operation 'Execute_stored_procedure_(V2)' of type 'OpenApiConnection' is not valid. Error details: The API operation 'ExecuteProcedure_V2' requires the property 'parameters/Paramenter1Name' to be a string of maximum length '-1' but is of length '14'.
Has anyone faced a similar issue? Our code is working fine before, but we are facing this error since yesterday(March 23rd)
 
13 REPLIES 13

Hi @mike528,

 

Thanks for reply.

I tried with your solution by replacing my json field column in procedure with nvarchar(MAX) to nvarchar(4000) and it worked, but MAX is required for this field, this is just work around, it cant be solution.

I need to raise ticket for that as well.

Also how to build a customer connector that will write to SQL DB correctly, please provide any links if you have.

Hi,

 

I had exactly the same issue. My SP was working fine, until I had to make a change to my flow (I needed to edit the json response), and it suddenly stopped working.  Changing the parameter in SQL from nvarchar(MAX) to nvarchar(4000) worked and fixed the issue.  I will have to watch for when Microsoft correct it so that I can revert back to nvarchar(MAX) on the SPside.

 

Thanks to all in this link for the solution guidance.

 

Regards

Lael

Thanks @Andre 

 

I was trying to pass very long XML string from Flow to a Stored Procedure, and was getting the same error using the XML data type on the Stored Proc side. So thanks to your post, I firstly changed my flow from "Execute a Stored Proc v2" to "Execute a SQL Query v2", and then I also changed my SQL stored proc parameter type from XML to varchar(max), and it worked. 

 

 

 

 

mike528
Resolver II
Resolver II

Everyone,

 

I am very happy to report this bug has been fixed by Microsoft! After nearly 2 1/2 months of back and forth, varchar(max) are not supported again. The MS support team was very helpful in getting this escalated to the engineering team to finally fix this!

 

Thanks, 

Michael

Helpful resources

Announcements
Super User 2 - 2022 Congratulations 768x460.png

Welcome Super Users

The Super User program for 2022 - Season 2 has kicked off!

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.

<
Users online (4,673)