cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
JosephBoland
Helper I
Helper I

Flow Run command has "invalid number of arguments" error for any parameters

I'm attempting to pass parameters to a flow that is the button action in a PowerApp.  The action is <flow name>.Run().  No matter what arguments I give to Run, I get an "invalid number of arguments" error.  This implies that no arguments are accepted.  Is this the case?  Other discussions of Run seem to indicate that it does accept arguments.  In that case, what am I doing wrong?  And if it doesn't accept arguments, how else can these be delivered to the invoked flow?

11 REPLIES 11
v-yamao-msft
Community Support
Community Support

Hi JosephBoland,

 

Your flow is triggered by PowerApps button, then what’s the following action? Please share a screenshot of your flow configuration.


To test this issue, I have created a simple flow. The Flow is triggered by PowerApps, the following action is “SharePoint – Create item”.


In the SharePoint list, I have several columns including Single Line of Text, Number, Date and Time.


In the flow, I select the dynamic content “Ask in PowerApps” for all the fields.


The following screenshot is the flow configuration of my flow.
3.PNG


On the app, add a button and other needed controls. Then configure the button’s OnSelect property as:

'PowerApp->Createitem'.Run(TextInput1.Text,Value(TextInput2.Text),DatePicker1.SelectedDate,DatePicker2.SelectedDate,Label1.Text,TextInput3.Text)


Specifying parameter to each column, I don’t get the error message you mentioned.

4.PNG

 

Please try again with it on your side and take this doc for a reference:
https://docs.microsoft.com/en-us/powerapps/using-logic-flows

 

If you are still having the issue, please show me more details to help reproduce this issue on my side.


Best regards,
Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi Mabel,

 

As I understand your proposed solution, it does not work in my environment.  Screenshots are below; here's a description of the components:

 

  1. SharePoint online list called "Messages" with Message Title, Message Text, and Audience columns.
  2. PowerApps form with a "Send Message" button.
  3. Flow called "Send SMS Messages" that is triggered by the PowerApps form.
  4. The "Send Message" button's On Select action is "SendSMSMessages.Run()"
  5. It is not possible to add any parameters to the Run command.  Doing so results in the "Invalid number of arguments" error.

 

This shows the Run command when a Label control's Text property is added.  Same error with every other parameter I've tried.

 

PowerApps_Run_error.PNG

 

Here is a screenshot of the flow.  Note that another open issue with Microsoft, which apparently many others are having (see link below) is that Dynamic Content is not available for PowerApps.

Flow_PowerApps_no_dynamic_content_final.PNG

 

 

On the issue of missing "Dynamic Content" for PowerApps, see https://powerusers.microsoft.com/t5/Building-Flows/No-Dynamic-Content-Available-Ask-in-Powerapps-Mis....

Hi everyone,

 

Sorry if I'm a little too late, but I've been having this issue and just found the solution.  No tricks - it's pretty easy:

 

  1. Ensure the name of your flow matches the "Ask in Powerapps" Flow variable (all characters before the underscore) that you're trying to pass, i.e. if your variable's name is "Sendanemail_To," then your Flow must be named "Sendanemail"
  2. Check how many copies of the same variable exist as an option in your Flow by clicking on the variable and scrolling to the bottom of your variable option window that pops up.  The number of copies will determine the number of arguments that you must include in the Run command in PowerApps, i.e. if you have "Sendanemail_To, Sendanemail_To_1,Sendanemail_To_2" available, you'll need to include three arguments in your Run command.
  3. At this point you may have to force PowerApps to recogize the updated flow immediately by either or all: (a) restarting PowerApps, (b) turning the flow off and turning it back on,/re-doing the Flow from scratch or via copying the Flow and deleting the original, ensuring the remaining copy is named per step #1.
  4. In Powerapps, assign your Flow as usual, and format the Run command parameters per this example: Sendanemail.Run(Text1,Text2...) where "Text" is either a Label or TextInput (with ".Text" appended, of course) or if you'd like to pass text directly as a parameter, just include whatever text you need enclosed in quotation marks.  In my case, I can either pass an email address enclosed in quotes, an email address that's a DataCardValue/Label/TextInput, or User().Email if I wanted an email sent to the user.
  5. Lastly, make sure that your number of arguments matches the number of variables per step #2.  If you don't need that many variables, assign double-quotes ("") in place of the variable.
zeus
Advocate III
Advocate III

This is still hit and miss for me. I have already done "ask in powerapps" twice and powerapps thinks the flow has no arguments. I get the error warning (triangle with exclamation) icon.

 

It takes a couple of tries, coming back and forth between the two apps to sync.Frustrating... It would be less frustrating if it tells you how many arguments is expected. 

Anonymous
Not applicable

I am having the same error, just created an one command flow to test the parameters and on powerapps, when calling the flow I get an error message saying that the flow has 0 expected parameters.     "Invalid number of arguments (Received: 1 ; Expected: 0)

 

on flow, I created a task to send a simple email and added the variable from dynamic contents / Ask in Powerapps on the subject line.

 

 

 powerapp

Flow

Rashaad_Compass
Frequent Visitor

I was having the same issues. 

Once I got PowerApps setup, I had to recreate the flow. 

That fixed the issues. 

The Flow was expecting 3 paramenters, even though it showed 1.

 

dimi
Impactful Individual
Impactful Individual

What helped for me was to add the variables in flow by "Ask in powerapps", after that in the PowerApps portal in Action => Flows => click on the Flow that is in the second section for it to connect to the Flow and than your parameters will be recognized. See screenshot. Hope this helps someone Smiley LOL 

 

Screenshot:

https://imgur.com/W8VjNDX

 

 

365-Assist
Multi Super User
Multi Super User

I just had the same problem. Thanks to all the replies in this thread most gave me bits of solutions. Here is what I did to solve it.

 

  1. In the PowerApps remove the Button OnSelect Function Details

Annotation 2020-06-01 140549.jpg

2. In Power Automate removed the 'Update File Properties' Action

 

Annotation 2020-06-01 135526.jpg

3 In PowerApps - Removed the PowerAutomate Source

Annotation 2020-06-01 135851.jpg

4.  In Powerapps - Added in the Power Automate Source back

Annotation 2020-06-01 140115.jpg

 

5.In PowerApps - Added back the OnSelect Function

Annotation 2020-06-01 140929.jpg

 

6. In Power Automated added back the PowerApp fields

Annotation 2020-06-01 141047.jpg

 

I hope this helps someone.

kaiserjake
Regular Visitor

Can anyone spot the error in this command? PowerApps is saying Invalid Number of Arguments, received 2, expected 1.

 

Set(varFileLink, UploadtoCDTSIOISharePointSite.Run(Last(AttachmentControl.Attachments).Name, varBase64Only).sharepointfilelink)

marcoswnunes
Frequent Visitor

Alright, I had the same issue and it was driving me crazy. Everything was working fine then after an update on my power automate flow I started to get that same error message.


In my case the issue on my Powerapps trigger.

 

When I checked on my power automate I had the following message:

marcoswnunes_1-1648801948243.png
When I checked my workflow, I noticed there was 3 required content inputs(content_inputs, content_inputs_1 and content_inputs_2). 

 

marcoswnunes_2-1648802041430.png

 

I have no idea why other 2 content inputs were created. I tried to delete but I couldn't. Then I deleted my trigger the re-added it but those extra parameters still there. 

 

My solution was pass those extra parameters in my call on PowerApps so I could move on.

 ExporttoCSV.Run( "My power automate was expecting 3 paramets here" )

 

First: JSON(colDataExported,JSONFormat.IncludeBinaryData & JSONFormat.IgnoreUnsupportedTypes
Second: ""

Third:  ""

 

 

ExporttoCSV.Run(JSON(colDataExported,JSONFormat.IncludeBinaryData & JSONFormat.IgnoreUnsupportedTypes
),"","");

 

There were cases where I has several required paraments. You can peek code to check it:

 

marcoswnunes_3-1648802935322.png

 

marcoswnunes_4-1648803005893.png

 

 

Hope it helps someone in the future. 

 

 

 

 

 

  

Baudelaire
Helper II
Helper II

Yes, I ran into this myself recently.  There are still aspects of PowerApps that are immature, especially in terms of integration with other members of the PP family.  In my case, I had an integrated flow that itself called SQL stored procedures.  I had to change the SQL side, and therefore needed to change everything upstream including the Run method in the app.  No dice.  PowerApps would NOT let go of the original set of parameters.  Removed connection, renamed flow, refreshed dozens of times, exited the app, etc. etc.  It would not let go of the original parameter signature.  The only thing that worked was completely rebuilding the flow from scratch.  THAT is a massive waste of project development time.  So the issue for me was not setting up the integration - that worked as expected.  It was making a change to the parameters passed via the Ask In PowerApps connector.  They need to take the black box out of this equation and provide us with more control.  To duplicate it just create a Flow integration connection, in the flow add several Ask In Power Apps variables.  Save the flow and the app.  Go back into the flow and remove a few of the Ask In Power Apps variable implementations and save the flow.  Watch in bewilderment as Power Apps hangs on to the original parameter list.  Peek code on the trigger and notice that the original list of parameters is still there.  Only option is to remove the trigger and re-add everything and PRAY you don't make a mistake before saving, or rebuild the whole thing (either option could take similar time depending on the complexity of the flow).  SMH as I ponder the collective number of development hours ($$$) wasted by everyone out there who has dealt with this.

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (5,377)