Unanswered

MS SQL Server stored procedure plugin parameters

(0) Share

Report

Posted on by Twon

Does anyone know how to create input parameters for plugin? There are only two options for Parameters section in Plugin definition

How will the bot fill this input?
1. Dynamically fill with best option (default)
2. Set Value

When I change to set value I can set only one value, but my stored procedure has few parameters. Does anyone know how to cope with that?

Categories:

General topics

1.png

I have the same question (0)

All responses (7)

Answers (0)

adilei on at

Like (0)

Report

Which connector and action are you using in this plugin?

Was this reply helpful? Yes No
Twon 22 on at

Like (0)

Report

@adilei SQL Server connector, Execute stored procedure (V2)

Was this reply helpful? Yes No
adilei on at

Like (0)

Report

So when loading "execute stored procedure" as a plugin, Copilot Studio does not dynamically identify the parameters for the procedure? If that is the case, consider wrapping the connector with a Power Automate flow, and load the flow as a plugin instead.

Was this reply helpful? Yes No
Twon 22 on at

Like (0)

Report

It does not. Moreover it's not establishing connection realtime like Power Platform does, thanks to which you see there available names of stored procedures on the dropdown list. Please look at attached screenshots. There are two same options for each connection parameter(Server, Database, Procedure, Parameters). Field is called "How will the bot fill this input?"
1. Set as value - where you can set one value(which for me for now in Parameters case doesn't make sense as you can have multiple parameters there, unless you can fill out all parameters in one line - which I don't know how to do here.)
2. Dynamically fill with best option (default) - which I have no idea of how it works.

I would rather use directly connector in the Plugin section, Power Automate flow might be slower than direct connector implementation.
Why it doesn't work? Does that mean there is a bug? Or how to set it up?

options.png

popup.png

Was this reply helpful? Yes No
adilei on at

Like (0)

Report

Sorry for missing your reply. Plugins are currently in preview, and currently not all connectors flawlessly translate to plugins. For now, I suggest the Power Automate approach - I'm not sure the latency is going to be noticeable, but you will have to verify.

Was this reply helpful? Yes No
Twon 22 on at

Like (0)

Report

Hi @adilei thanks for your insight.
I'm not even at this point to test it, it's because I simply don't how to fill in parameters. Could you please take a look on the screenshot, do you know how to pass 4 arguments in the last line which is called "Parameters list"?
If I fill in correctly and then it will turn out that this functionality doesn't work yet, then fine. But again for now I don't even know how to pass arguments which is very first step.

Was this reply helpful? Yes No
adilei on at

Like (0)

Report

My suggestion pointed to a different pattern: 1. Create a Power Automate flow that calls "Execute Stored Procedure". Make sure that the input parameters for your flow are the ones needed to run the stored procedure. 2. Load the flow itself as a plugin action in Copilot Studio, instead of loading the connector directly

Was this reply helpful? Yes No