Unanswered

Bug in Power Automate Flow argument count validation where multiple optional inputs

(1) Share

Report

Posted on by wjamesw

I think I've identified a bug whereby PowerApps does not read a Power Automate Flow definition correctly where there are multiple optional inputs to the Flow Trigger "PowerApps (V2)". The App is therefore not capable of triggering the Flow with all the inputs as the formula is marked as an error.

To replicate this, I created a test flow with 3 inputs; I left the first set to required and changed the other 2 inputs to optional:

{
 "kind": "PowerAppV2",
 "inputs": {
 "schema": {
 "type": "object",
 "properties": {
 "text": {
 "title": "Input1",
 "type": "string",
 "x-ms-dynamically-added": true,
 "description": "Please enter your input",
 "x-ms-content-hint": "TEXT"
 },
 "text_1": {
 "title": "Input2",
 "type": "string",
 "x-ms-dynamically-added": true,
 "description": "Please enter your input",
 "x-ms-content-hint": "TEXT"
 },
 "text_2": {
 "title": "Input3",
 "type": "string",
 "x-ms-dynamically-added": true,
 "description": "Please enter your input",
 "x-ms-content-hint": "TEXT"
 }
 },
 "required": [
 "text"
 ]
 }
 }
}

Then when trying to run the Flow from a Power App with all the arguments, the error "Invalid number of arguments: received 3, expected 1-2" occurs:

Screenshot 2023-08-22 064541.png

I think this should accept 1-3 arguments.

Categories:

Building Power Apps

All responses (3)

Answers (0)

Sort by

poweractivate 11,078 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

@wjamesw

Are you sure you didn't initially have only the one required and the one optional, saved, added to the Canvas app and then added the third in a bit later? Be sure to go to the Flow in the Canvas App, use the ellipses and click on Refresh and then it might update correctly, after making sure your Flow that has the 3 arguments was saved correctly.

Also try this one more time from the beginning with a new Canvas App and new Flow from scratch, just to be sure.

If you are sure you did that and this may indeed be a bug, you may want to file a support ticket here with your findings.
wjamesw 7 on at

Like
a
(1)

Report
Copy link

Link copied!

Thanks for the quick response!

All good ideas; though the above test was the new flow and app created from scratch. The app was created after the flow was finalised so no out of date definition, though I did try a refresh.

I will raise a support ticket as suggested.
wjameswilliams 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Microsoft Support confirmed that the solution is to submit all optional arguments as a record, for example:

Run(TextInput1.Text,{text_1:TextInput2.Text,text_2:TextInput3.Text})

So from Power App's perspective, all optional arguments together count as one argument.