Execute Stored Procedure (V2) not finding stored procedure on the server

[shoaibmaroof7]

The Execute Stored Procedure (V2) does find procedures. It has become a blocker.

I get the following message:

The dynamic operation request to API 'sql' operation 'GetProcedure_V2' failed with status code 'BadRequest'. This may indicate invalid input parameters. Error response: { "status": 400, "message": "The key didn't match any rows in the table. inner exception: The key didn't match any rows in the table. clientRequestId: 9a1447e2-5c7e-4d93-8747-53ce6c8ad671", "error": { "message": "The key didn't match any rows in the table. inner exception: The key didn't match any rows in the table." }, "source": "sql-ukw.logic-ase-ukwest.p.azurewebsites.net" }

[shoaibmaroof7]

[tsexton]

I am having this issue. Were you able to find a resolution? Thx.

[tsexton]

For others who may have this problem, the solution for me was to connect to the SQL Server with SSMS > right-click on the database > Properties > Permissions page > select the user Power Automate is connecting as > in the bottom half of the screen, on the "Explicit" tab, scroll down to the "Execute" line and check the box in the Grant column. The change didn't take effect immediately in Power Automate, but by clicking the ellipse on the Execute Stored Procedure (V2) box and adding a new connection (with the same settings), I was able to see all my procs as options immediately. Hope that helps someone!

[acrs2022]

thanks, it works