Power Apps

Power Apps Fx flow run formula not recognizing additional parameter in flow

(1) Share

Report

Posted on by Cgangweg01

878 Super User 2026 Season 1

Hello -

To start ... I've refreshed and removed/added back the power automate flow to the canvas app several times.

The expression in the following screen shot executes successfully. It sends the data to the flow and the flow runs without error.

You can see that there are 7 data sets being provided. 5 json/collections and then 2 other fields.

I've added an eighth parameter to the flow which is optional.

When I try to add the eighth parameter data set to the power app formula, I get the following error.

"Invalid number of arguments: received 8, expected 6-7."

I've tried numerous syntaxes and expressions to get the 6,7,8 parameters to be accepted to no avail.

Appreciate if anyone can help me trouble shoot this?!!!!!

Categories:

Building Power Apps

I have the same question (0)

All responses (6)

Answers (0)

Sort by

WarrenBelz 155,642 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @Cgangweg01,

When you removed it, did you save and re-open the app before re-adding it ? Also try saving a copy of the Flow with a new name and adding that instead.

As well, have you tried making the last parameter non-optional and if it works then, put it back to optional.

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥
Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No
Suggested answer

vipuljain03 696 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @Cgangweg01,

In your flow trigger, turn the 8th parameter from Optional to Required. Save the flow and Refresh it inside Power Apps.

Type out your formula with all 8 arguments. Because it is marked required, Power Apps will be forced to look for exactly 8 arguments instead of guessing a flexible range (6-7).

Once the app successfully saves with no errors, you can safely turn it back to Optional in Power Automate if needed.

======================

If this reply helped you, please mark this reply as suggested answer ✔️ and give it a like to help others in the community find the answer too!

Thanks,

Vipul

Was this reply helpful? Yes No
Suggested answer

BCBuizer 22,814 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Hi @Cgangweg01,

When dealing with mulitple optional parameters, they have to be passed as an object in a single argument:

Set( varFlowResponse, DMPversionCreateFeatureinADOfromAssistant. Run( JSON( colAIFeatureDescription, JSONFormat. IgnoreBinaryData & JSONFormat. IgnoreUnsupportedTypes ), JSON( colAIFeatureTitle, JSONFormat. IgnoreBinaryData & JSONFormat. IgnoreUnsupportedTypes ), JSON( colAIAcceptanceCriteria, JSONFormat. IgnoreBinaryData & JSONFormat. IgnoreUnsupportedTypes ), JSON( colAIBusinessoutcomes, JSONFormat. IgnoreBinaryData & JSONFormat. IgnoreUnsupportedTypes ), JSON( colAINonFuncitonalRequirements, JSONFormat. IgnoreBinaryData & JSONFormat. IgnoreUnsupportedTypes ), Text(cmbBoxADOProjects.Selected.name), { text_6:txtInptworkItemNumber.Text, text_7:cmbBoxTShirtSize.Selected.Value } ) )

Please correct any typos since I captured the formula with OCR.

If this reply helped you in any way, please give it a Like 💜 and in case it resolved your issue, please mark it as the Verified Answer ✅.

Was this reply helpful? Yes No
Cgangweg01 878 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hello @WarrenBelz and @vipuljain03 -Thanks for the replies. I got things to work partially with your suggestions. I was just going to accept that they'd be mandatory and deal with that in the flow.

Hi @BCBuizer

Thank you for that information. It worked. Both flow parameters are now optional and grouped as an object in the run flow argument. However, when I don't select a value in cmbBoxTShirtSize (which is also optional in the app) and submit, Power Apps just spins and the flow is not triggered. I've never had this before. There are no power app errors and no failed flow run so I can't even give you details other than that.

Can you provide any suggestions to address this?

I suspect I'm going to have to create a variable for text_7 that resolves to either cmbBoxTShirtSize.Selected.Value or something that represents null perhaps. Does that make sense?

Thanks again!

Was this reply helpful? Yes No
WarrenBelz 155,642 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @Cgangweg01,

Your initial post did not make it evident that the 7th parameter was also optional. If @BCBuizer's suggestion works, than that s good, but it is not my understanding - you still need to pass somthing for "optional" parameters, even if it is Blank() or "" - it is confusing as they are "optional" to have values in the Flow (Blank() is not really a value matching the type requrested), but Power Apps will still require the correct number of parameters.

Was this reply helpful? Yes No
Suggested answer

BCBuizer 22,814 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi @Cgangweg01,

Passing an optional parameter with a blank or null value will cause the behaviour you described. There are multiple ways to prevent this from happening, but usually works best for me is to pass a value that is recognized in the flow as blank/null using the Coalesce() function, for instance "":

Set( varFlowResponse, DMPversionCreateFeatureinADOfromAssistant. Run( JSON( colAIFeatureDescription, JSONFormat. IgnoreBinaryData & JSONFormat. IgnoreUnsupportedTypes ), JSON( colAIFeatureTitle, JSONFormat. IgnoreBinaryData & JSONFormat. IgnoreUnsupportedTypes ), JSON( colAIAcceptanceCriteria, JSONFormat. IgnoreBinaryData & JSONFormat. IgnoreUnsupportedTypes ), JSON( colAIBusinessoutcomes, JSONFormat. IgnoreBinaryData & JSONFormat. IgnoreUnsupportedTypes ), JSON( colAINonFuncitonalRequirements, JSONFormat. IgnoreBinaryData & JSONFormat. IgnoreUnsupportedTypes ), Text(cmbBoxADOProjects.Selected.name), { text_6:Coalesce(txtInptworkItemNumber.Text,""), text_7:Coalesce(cmbBoxTShirtSize.Selected.Value,"") } ) )

What this function does, is to return the value of the firrst argument that is non-blank. So that means when cmbBoxTShirtSize.Selected.Value is blank, it will return "". On the Power Automate side you will need to make sure the flow can handle this and will not act in the same way as if a valid value was passed.

If this reply helped you in any way, please give it a Like 💜 and in case it resolved your issue, please mark it as the Verified Answer ✅.

Was this reply helpful? Yes No