Hello,
I have a flow that triggers with the click of a button. Which runs the store procedure. In the given screen below I have three different departments with fields. The user may or may not fill in all the details requested. Fields are optional. And I have the same rule (optional fields) set up on the SQL side as well.
When I try to test this flow with random fields completed it works 1-2 times and then starts to throw an error: Invalid parameter.
Any suggestions?
Thanks,
Omi
Solved! Go to Solution.
In my experience Power Automate doesn't pass null values in JSON and that is what is used between Power Apps and Flow. It may still work depending on the order of your optional parameters. But as I said, I just don't use them because they cause issues.
When calling a flow from Power apps, Power Automate doesn't support optional parameters. So you have to supply all the parameters. There are two ways to do this.
1) load the optional parameters with a default value like "null" and then process them in the flow.
2) Pass all the parameters as a single JSON object. Then parse the object once you are in flow. Since there is only one parameter, the JSON object, you don't have to worry about optional values. You can leave them blank in the JSON.
Hi @Pstork1 ,
Yes, I meant optional as in we are passing null value whichever fields are not filled. It just happens with this flow. But other flows similar to this are working fine.
Thanks,
Omi
In my experience Power Automate doesn't pass null values in JSON and that is what is used between Power Apps and Flow. It may still work depending on the order of your optional parameters. But as I said, I just don't use them because they cause issues.
User | Count |
---|---|
251 | |
102 | |
94 | |
47 | |
37 |