Hi all,
I have a flow that currently starts when a new item is added to a SharePoint list.
I would like to start the flow from within a Power App (by clicking a button).
1) I am not sure if and how it can be done
2) how do I "tell" the Flow which item it should process.
The background of this operation is, that I want to run the flow with the currently logged in user.
Any support is really appreciated.
Solved! Go to Solution.
GetItem_ID is the parameter. Inserting the Ask in Power Apps creates that field using the name of the action and the field. In this case that is Get Item and ID. If you now save and add that flow to your power app button Intellisense should prompt you to put that parameter in the Run() function. Make sure its the right data type. It should be an integer.
To trigger a flow from a Power Apps button it has to use a Power Apps manual trigger. So to convert an existing flow to trigger from Power Apps you need to remove the automated trigger and replace it with a manual Power Apps trigger. You'll also need to adjust the flow to provide any information that was originally provided by the automated trigger. So if a flow was originally trigger by an item being changed in SharePoint you would replace the trigger and add a Get Item action. Then pass the ID of the SharePoint item to be used in the Get Item. You can't have a flow that is triggered both automatically and manually from a Power App.
Hi @Pstork1 and thanks for your answer!
I did follow your description but I am not sure what to do in the following step:
In PowerApps I do have an ID for the current item, that is written to SharePoint.
And the connection to PowerApps is not done yet, I believe...
I might not understand correctly. Could you please assist again?
So it looks like you have already used the 'Ask in Power Apps' dynamic content to generate a parameter to pass the ID. insert the GetItem_Id dynamic content into the id field of Get Item. Then Save the flow.
On the Power Apps side. Highlight the button you want to use and access the OnSelect property. Then navigate to 'Power Automate; on the Action menu. You should see the flow you just saved in the list. Click on the flow to insert it into the Power App. That will add flowname.run( to the OnSelect property. Intelisense will prompt you to add any needed parameters. In your case its probably just 'GetItem_id'. Supply the ID of the SharePoint item there then close the parentheses. When you click that button it should run the flow on the SharePoint item you supplied the ID for.
Hi @Pstork1 ,
the 'GetItem_id' is not done by me...I'm not sure, where it come from 🙂
In PowerApps I use a variable to read the ID of the newly created item in SharePoint:
Set(OrderIDVar,
Patch(Order, Defaults(Order),
{
Purchaser: {'odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
ODataType: Blank(),
Claims:Concatenate("i:0#.f|membership|",User().Email),
DisplayName:User().FullName,
Email:User().Email,
Department:"",
JobTitle:"",
Picture:""
},
Title:"User created by PowerApps | " & Text( Now(),"[$-da]dd/mm/yyyy hh:mm:ss"),
Comment: inp_comments.Text,
Total: Text(Sum(basket, itemprice), "[$-en-US]###,###.00"),
Approver:{'odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",
ODataType: Blank(),
Claims:Concatenate("i:0#.f|membership|",inp_manager.Selected.Mail),
DisplayName:User().FullName,
Email:User().Email,
Department:"",
JobTitle:"",
Picture:""
}
}
).ID)
So, what comes in the brackets 'name of flow'.Run(xxxx)? Is it the name of the Variable (OrderIDVar)?
The GetItem_ID came from someone adding the Ask in Power Apps dynamic content to an action called GetItem. Is someone else also editing the flow? And yes, the variable would be what you would supply in the RUN() command where you have the xxxx.
This walkthrough explains the whole process.
Start a flow in a canvas app - Power Apps | Microsoft Docs
Hi @Pstork1
I can not get rid of the GetItem_ID.
But in PowerApps I can see this as well.
I just created the flow, so there should be nobody else editing it.
When entering the name of the variable (OrderIDVar) in the brackets, it gives me an error.
So, something might not be fitting. Any other idea?
Remove the Power Apps trigger from the flow and re-add it. That should get rid of the GetItem_ID varable. Then after the trigger is re-added you can create a new parameter by inserting the Ask in Power Apps entry into the ID field of the Get Item. then save the flow.
Next remove the flow from the Power Apps button and re-add it. It should ask for the variable you created.
Hello @Pstork1
thank you very much for your patience.
I just removed the trigger and re-added it.
Then, when clicking into the Id field, it shows me "Ask in PowerApps".
But when I click on it, it puts GetItem_id into the field.
I am not able to create a new parameter...
GetItem_ID is the parameter. Inserting the Ask in Power Apps creates that field using the name of the action and the field. In this case that is Get Item and ID. If you now save and add that flow to your power app button Intellisense should prompt you to put that parameter in the Run() function. Make sure its the right data type. It should be an integer.
Hi @Pstork1
thanks a lot for your help. Now I did understand 🙂 It works now!
I have one more thing:
As mentioned above I am doing all that because I would like to send an e-mail out as the logged-in user in PowerApps.
So, for example, I ordered something in PowerApps and the flow should send an e-mail to the ticket system from my e-mail account. How do I configure that?
In the flow use the Send an Email action and fill in your email address as the From. The issue you will run into is that whoever pushes the button in the power app will need "Send As" permission for your mailbox or the email will fail because the flow runs in the context of the user running the power app.
Hi @Frankie70 , for the 'Send an email' action in your flow, you would need to ask the 'From' parameter in your PowerApp also. After you have changed your flow to ask that field, you should update the button in your PowerApp that calls the flow and add the User().Email parameter to it. This way, the email will be sent from the user that is using the PowerApp.
You may have to remove the flow from your app and re-add it after you have changed the flow in order for PowerApps to take into account the additional parameter that the flow needs.
I mean it the other way around.
A mail should go to the ticket system from the user who ordered (so that the user will get a ticket number from the ticket system and can track the progress of the ticket).
As you described here:
https://powerusers.microsoft.com/t5/Building-Flows/sending-mail-as-item-creator/td-p/711376
Or did I misunderstand?
Then you need to pass the email of the user who pushes the button as another parameter and use that to fill in the From field in the email action.
Hello @Pstork1
thanks a lot! This did work, although now ALL mails are sent from the email address that is used in PowerApps.
There are some Mails in the Flow that should be sent from a Service Account.
Under "my connections" in the action I checked a service account I want to send the mail with!
Any Idea why this is happening?
As I mentioned above. When you start a flow from Power Apps the flow will run in the context of the user who triggers the flow. That will apply no matter what account the connection was originally sent to. You can manually override the From field on some of the email actions. But doing that will require that the person running the flow has "Send as" permission to that mailbox. For large groups of user's that usually not practical.
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!
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 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 SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (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. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 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 Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 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 Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
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.
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