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

Passing Parameters from a Flow to an App

I've got a test app that is intended to run the Excel Flow function "Get row" and retrieve a given row of data from a simple 4 column Excel spreadsheet on OneDrive and populate 4 TextInput fields in the App.    From a slightly different Community example, I reckon my Flow needs to have a trigger, i.e. PowerApps, a "Get row" step, and a "Filter Array" step following that.   However, I don't know how to use the "Filter Array" and related Dynamic Content to capture the data and get it to my App.   My attempt at the Flow so far is shown in the image below.   The expression in the "From" field of the "Filter array" step is

@and(not(empty(item()?['Row'])),not(empty(item()?['Column A'])),not(empty(item()?['Column B'])),not(empty(item()?['Column C'])) )

All help is greatly appreciated.  Thx

Cheers,

Bob G

 

 

Pwr App Screen Shot-22.jpg

1 ACCEPTED SOLUTION

Accepted Solutions

Kris, Happy New Year and thanks for getting back to me a few days ago. It took me a few days to get to your instructions but they helped me get my test flow of “Get row” working with my app😊 The main ingredients to the solution were as follows: You said: “Based on the screenshot that you provided, I think you have something wrong with the 'Get row'.Run() function within your formula.” The above was correct. My initial expression was: “ClearCollect(RecordsCollection,Get row.Run(Label2_9.Text))”. Pwr Apps didn’t like the space between Get and row. I had labeled my flow “Get row”. Not really knowing that the space was a problem, I relabeled my flow “Getrow” and changed the expression in my app accordingly. The error went away! You had additionally said: If you wantt to use 'Get row'.Run() function within your app, you need to add your 'Get row' flow connection within your app." I didn’t know how to add the flow connection at first but, your reference to the Pwr App help text ( https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/using-logic-flows#add-a-flow-to-an-app ) eventually led me to try something that did the trick. I inserted a test button then, using the Action tab and the Flow subtab, I associated my flow with the button. That produced the prompt “Getrow.Run(“ and I kinda new that I was on the right track. When I completed the expression using the last part of the expression mentioned two paragraphs above, the other error messages associated with my Input Text fields also went away! The error messages also stayed away even after I deleted the added test button. I conclude from this that one way to *add a flow connection* to an app is to create a button and correctly assign the flow to it. Once done and saved, the connection is established. NOTE: I had fixed a minor error in one column references in the flow’s Response Body script from your initial response before clicking the newly edited Start Test Flow button. The correct column reference seems to be Column_x0020_B_x0020_ vs Column_x0020_B. Beforehand, I also added the appropriate version of the expression you advised for target TextInput fields, First(RecordsCollection).ColumnName, to 3 additional TextInput fields to ensure that all 4 columns in my Excel spreadsheet were had targets for the “Get row” Action. Many thanks again for your expert and clearly stated responses to my questions. Cheers, Bob G.

View solution in original post

9 REPLIES 9
v-xida-msft
Community Support
Community Support

Hi @BobG

Do you want to pass the retrieved Excel data from your flow to your app?

Could you please share a bit more about the data structure of your Excel table?

Do you want to get a specific row in your Excel table based on the Row Id in your flow?

If you want to get a specific row in your Excel table based on the Row Id in your flow, I think it is not necessary to add a "Filter Array" action within your app, because the "Get row" action could only retrieve one record.

If you want to retrieve all records in your Excel table, and find the specific record based on the filter condition within the "Filter Array" action. I think there is something wrong with your "Filter Array" action. The From field of the "Filter Array" action is required to provided an Array data rather than a filter condition. You should modify your flow as below:5.JPG

 

If you just want to get a specific row in your Excel table based on the Row Id (passed from your app) in your flow, and then pass returned result to your app, please take a try with the following workaround:

Flow's configuration as below:

6.JPG

Add a "Response" action within your flow, set the Body field to Body dynamic content of the "Get row" action. Set the Response Body JSON schema field to following:

{
    "type": "object",
    "properties": {
        "@@odata.context": {
            "type": "string"
        },
        "@@odata.etag": {
            "type": "string"
        },
        "ItemInternalId": {
            "type": "string"
        },
        "ID": {
            "type": "string"
        },
        "EmployeeName": {
            "type": "string"
        },
        "Department": {
            "type": "string"
        },
        "IsVolunteer": {
            "type": "string"
        },
        "__PowerAppsId__": {
            "type": "string"
        }
    }
}

On your side, you should type:

{
    "type": "object",
    "properties": {
        "@@odata.context": {
            "type": "string"
        },
        "@@odata.etag": {
            "type": "string"
        },
        "ItemInternalId": {
            "type": "string"
        },
        "Row": {
            "type": "string"
        },
        "Column_x0020_A": {
            "type": "string"
        },
        "Column_x0020_B": {
            "type": "string"
        },
        "Column_x0020_C": {
            "type": "string"
        },
        "__PowerAppsId__": {
            "type": "string"
        }
    }
}

Note: The ID, EmployeeName, Departemnt and IsVolunteer are all columns in my Excel table.

 

App's configuration as below:

7.JPG

Set the OnSelect property of the "Collect" button to following:

ClearCollect(RecordsCollection, '20181228_case10'.Run(TextInput1.Text))

On your side, you should type:

ClearCollect(RecordsCollection, 'YourFlowName'.Run("Row Id you want to pass to your flow"))

The RecordsCollection stored well as below:8.JPG

If you want to reference the returned value within your Text Input box, please take a try with the following formula:

Set the Default property of the Text Input box to following:

First(RecordsCollection).ColumnName

e.g. If you want to reference the Column A value from the RecordsCollection, please take a try with the following formula:

First(RecordsCollection).Column_x0020_A

Please check and see if the following blog would help in your scenario:

https://powerapps.microsoft.com/en-us/blog/return-an-array-from-flow-to-powerapps-response-method/

More details about starting a flow from an app, please check the following article:

Start a flow from an app

 

Best regards,

Kris

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

Kris,

    Many thanks for the comprehensive and clear response to my post.    I've tried the single row solution and the Flow runs is Test mode with no errors.   It looks like the following....Pwr Apps Screen Shot-24.jpg

 

My App has one, "Start Test Flow", that includes the expression

Collect(RecordsCollection, {Pressed: Button3_1.Pressed}) 

which corresponds to your instructions and which, I believe, creates the Collection "RecordsCollection" and a Text Input field "TextInput8_1" with the expression

First(RecordsCollection).Row   (Note: Row is the name of my first column.  I also tried your exact expression with Column_x0020_A, my second column, but still got the error message)

intended to recieve the data from the first column of my Excel table when the Flow eventually runs.   At the moment, there is a error in that formula which states "Name isn't valid.  This identifier isn't recognized.  Etc..."   

My Spreadsheet is shown in the next image and my App is shown in the image following that.

It seems that you got me very close to the finish line on this so I'm hoping that the next step is easy for you to figure out.   Thanks again for the help!

Pwr App Screen Shot-12.jpg

 

Last image for prior post....

Pwr Apps Screen Shot-26.jpg

 

Another postscript....the script in my Flow Response step is as follows which should be exactly as you recommended....

 

{

    "type": "object",

    "properties": {

        "@@odata.context": {

            "type": "string"

        }

 

        "@@odata.etag": {

            "type": "string"

        },

        "ItemInternalId": {

            "type": "string"

        },

        "Row": {

            "type": "string"

        },

        "Column_x0020_A": {

            "type": "string"

        },

        "Column_x0020_B": {

            "type": "string"

        },

        "Column_x0020_C": {

            "type": "string"

        },

        "__PowerAppsId__": {

            "type": "string"

        }

    }

}

Kris,

   To avoid your wasting time, I need to correct a big error in my first response to you.

 

CORRECTION:  The expression for my "Start Test Flow" button was not correct and, because of that, my Flow did not run without errors.    In fact, I'm getting a error message associated with the expression below which, as near as I can tell is consistent with your instructions.

Expression: ClearCollect(RecordsCollection,'Get row'.Run(Label2_9.Text))  

The error messages associated with this expression are:

     1. Invocation of unknown or unsupported function

    2.  The function 'ClearCollect' has some invalid arguments

The current state of my App looks like this...

Pwr Apps Screen Shot-28.jpg

Hi @BobG,

Could you please share more details about the error message within your app?

Based on the screenshot that you provided, I think you have something wrong with the 'Get row'.Run() function within your formula.

If you want to use 'Get row'.Run() function within your app, you need to add your 'Get row' flow connection within your app.

More details about adding a flow connection within an app, please check the following article:

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/using-logic-flows#add-a-flow-to-an-app

Please check if you have added your 'Get row' flow connection within your app. Also please check if you have deleted or renamed the specific flow within your Flow Environment.

In addition, please also check if you have typed proper argument or arguments within the 'Get row'.Run() function. The parameter value(s) you typed within the 'Get row'.Run() function must match the arguments you specified within your flow.

If the issue still exists, please consider take a try to re-create a new app, then add your 'Get row' flow connection within it, try your formula again to check if the issue is solved.

 

Best regards,

Kris

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

Kris, Happy New Year and thanks for getting back to me a few days ago. It took me a few days to get to your instructions but they helped me get my test flow of “Get row” working with my app😊 The main ingredients to the solution were as follows: You said: “Based on the screenshot that you provided, I think you have something wrong with the 'Get row'.Run() function within your formula.” The above was correct. My initial expression was: “ClearCollect(RecordsCollection,Get row.Run(Label2_9.Text))”. Pwr Apps didn’t like the space between Get and row. I had labeled my flow “Get row”. Not really knowing that the space was a problem, I relabeled my flow “Getrow” and changed the expression in my app accordingly. The error went away! You had additionally said: If you wantt to use 'Get row'.Run() function within your app, you need to add your 'Get row' flow connection within your app." I didn’t know how to add the flow connection at first but, your reference to the Pwr App help text ( https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/using-logic-flows#add-a-flow-to-an-app ) eventually led me to try something that did the trick. I inserted a test button then, using the Action tab and the Flow subtab, I associated my flow with the button. That produced the prompt “Getrow.Run(“ and I kinda new that I was on the right track. When I completed the expression using the last part of the expression mentioned two paragraphs above, the other error messages associated with my Input Text fields also went away! The error messages also stayed away even after I deleted the added test button. I conclude from this that one way to *add a flow connection* to an app is to create a button and correctly assign the flow to it. Once done and saved, the connection is established. NOTE: I had fixed a minor error in one column references in the flow’s Response Body script from your initial response before clicking the newly edited Start Test Flow button. The correct column reference seems to be Column_x0020_B_x0020_ vs Column_x0020_B. Beforehand, I also added the appropriate version of the expression you advised for target TextInput fields, First(RecordsCollection).ColumnName, to 3 additional TextInput fields to ensure that all 4 columns in my Excel spreadsheet were had targets for the “Get row” Action. Many thanks again for your expert and clearly stated responses to my questions. Cheers, Bob G.
BobG
Helper I
Helper I

Kris,

   The solution that you provided for me was very helpful but I didn't realize until later that the script you provided for the Reponse Body passed absolute values to my app as opposed to spreadsheet values.   I'd appreciate it if you could send me a revised script that would retrieve the spreadsheet values dynamically.   Thx.

Cheers,

Bob G.

Kris, Please ignore my last response. Upon further testing, I've discovered that only two rows, 7 and 8, display the errant behavior that led me to believe that your script was sending absolute values to me.   I'm pretty sure that, along the way, I corrupted rows 7 and 8, which will probably explain this behavior.   I'll do some more work before crying wolf again!

Cheers,

Bob G.

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

Users online (1,612)