cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Passing dropdown selections to Flow

I have created an App that will input three different fields and create an ADO request:  2 text fields and one dropdown field made in PowerApps.

 

When I attempt to pass the variables into my flow I get this message in PowerApps - "The function Run has some invalid arguments".  I have searched on the found some postings referring to using "Dropdown.Selected.Value" in the Run command but that doesn't appear to work either.  There are red lines under the Selected.Value part.

 

Here is what I am putting in: FLOW.Run(Createaworkitem_Title,Createaworkitem_Description,Createaworkitem_OtherFields.Selected.Value); Navigate(Success, ScreenTransition.None)


1 ACCEPTED SOLUTION

Accepted Solutions

@astockli 

Ah, so now the story unfolds...

Your signature for your Flow to PowerApps is Text, Text, Record

However, the reality is you want Text, Text, Text to go in.

Your original Formula in your first post is fine.  The problem is your Flow definition. 

The unfortunate part is that you can't easily change the input types on Flow for PowerApps.  Once it has determined that you needed a record (if you needed it or not), it will remember that for its signature.

You have two (sort of three) choices:

1) Rebuild your Flow from scratch and make sure you are getting only string type parameters/input from Ask PowerApps

2) Put in another Ask PowerApps parameter in your existing Flow for the text value.  This will add another parameter to your flow signature in powerapps.  For the record parameter, you can then substitute a {} for an empty record (as you'll not use it anyway).

3ish) There is a Flow editor that will alow you to edit the JSON definition of your Flow.  There you can manually change the definition.  I would only recommend this if you have already created a complex Flow and starting from scratch is not an option.

 

I hope that helps clear it up for you.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

View solution in original post

11 REPLIES 11

@astockli 

What is the error for the red lines when you hover over it?

What are the Items for your DropDown?  If it is a record from a DataSource, then you would need to specify the column/field name rather than a Value.  In other words, the options available on the "Selected" will depend on the items you have in the control.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

It says "Invalid argument (Text).  Expecting a record value instead"    The list is just one created within PowerApps:

["","Value1","Value2","Value3"]

@astockli 

So there it is...look at your Flow parameters that come up in your Formula - it is looking for a Record not a Text.

If you pass the Selected.Value, you are passing a text item to it and it is not what it wants.  You can try to drop the DropDown.Selected.Value and just pass the DropDown.Selected instead, but I would have a serious look at your Flow as you seem to be thinking that passing a text value is what you want.  If not, then yes, pass it the record.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!
v-monli-msft
Community Support
Community Support

Hi @astockli ,

 

Are both Createaworkitem_Title and Createaworkitem_DescriptionI text controls' names? If so, I think the issue could be that you didn't add ".Text" at the end of text control. The formula should be:

FLOW.Run(Createaworkitem_Title.Text,Createaworkitem_Description.Text,Createaworkitem_OtherFields.Selected.Value); Navigate(Success, ScreenTransition.None)

Regards,

Mona

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

@RandyHayes 

 

I tried the .Selected and the app now runs but it is passing a blank value to the flow.

 

I am using an Azure DevOps connector in Flow with the Product field equal to Createaworkitem_OtherFields.  (see attached)  In PowerApps it is a custom dropdown field.  

 

I'm new to PowerApps so I'm not sure how to pass it as a Record if that is what needs to be done.

 

 

@astockli 

So it seems that the type mismatch on the parameter you were passing was the primary issue...now to get the correct information.

First I would reflect on @v-monli-msft 's posting.  Make sure you are passing the .Text if those first parameters are Controls.  If they are just fields from your datasource or variables, then you should be fine there.

You can always look at a previous run of Flow results and click on the top block of your flow to expand it.  That will show you everything that was passed in and what type it is.

Now for that last parameter...do you want a text value to go to flow, or a record?

What function are you calling on the DevOps connector? 

Make sure you are passing the proper type that the function wants.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

@RandyHayes 

 

I am using the Create a work item connector with Azure DevOps.  All three fields are used in flow as an "Ask in PowerApps" value.  The first 2 are input directly from the App and the third is the custom dropdown in PowerApps.  I would think if it came in as a text value it would work fine.  I tested this by editing the Flow and inputing a text value in place of the Createaworkitem_OtherFields item.  The Flow worked fine with this test and created the work item.

@astockli 

Ah, so now the story unfolds...

Your signature for your Flow to PowerApps is Text, Text, Record

However, the reality is you want Text, Text, Text to go in.

Your original Formula in your first post is fine.  The problem is your Flow definition. 

The unfortunate part is that you can't easily change the input types on Flow for PowerApps.  Once it has determined that you needed a record (if you needed it or not), it will remember that for its signature.

You have two (sort of three) choices:

1) Rebuild your Flow from scratch and make sure you are getting only string type parameters/input from Ask PowerApps

2) Put in another Ask PowerApps parameter in your existing Flow for the text value.  This will add another parameter to your flow signature in powerapps.  For the record parameter, you can then substitute a {} for an empty record (as you'll not use it anyway).

3ish) There is a Flow editor that will alow you to edit the JSON definition of your Flow.  There you can manually change the definition.  I would only recommend this if you have already created a complex Flow and starting from scratch is not an option.

 

I hope that helps clear it up for you.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

@RandyHayes 

 

I rebuilt my flow from scratch and initialized string variables for each of the parameters I passed from PowerApps.  Once I had that set up everything worked great.  Thanks for the help!

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Top Kudoed Authors
Users online (3,171)