Power Platform Community Forum Thread Details

Hello - I've built a handful of apps that call a PA flow from the OnSelect property of a button; however this is the first time I've encountered this problem where the flow is not triggering.

I've tested my flow manually in which I had to enter data for each of my variables in the flow and it succeeded. But, when I attempt to trigger the flow from my Power apps button, nothing happens. Any help would be greatly appreciated.

UI of my app with register and add to waitlist buttons in the gallery:

The OnSelect property of the Register button runs the flow to register. A separate flow runs the Add to waitlist button.

The variables from my flow which I have set in my power app:

My flow variables. Only the 1st three are actually being set from my app. The other variables I am setting in an Apply to each loop after getting values from a specified Sharepoint list.

The flow ran successfully when I tested it, but I had to manually enter values for each of the variables which I've set in power apps.

1st part of flow

2nd part of flow.

Part of the reason for the flow is there are calculations made to 2 different SP lists to keep track of Registered counts and update the Wait list counts and wait list order when someone cancels an RSVP. Also, I couldn't get the add event to the user's calendar to work, so I decided to try creating an ics file in Power Automate instead of using the action in Power Apps.

All of this is to say if someone has a better method for achieving what I want to do, I'd be most eager to learn.

Categories:

Building Power Apps

In the end, I believe what was causing my issues was that I was building the flows from Power Apps using a template (power Apps button to create item to send email) and this caused the app to need more variables than I wanted to use. So, instead I rebuilt my flows in my power apps from blank/scratch. This gave me more flexibility over the variables that I wanted to pass through from my app using the Ask in Power Apps option. Overall this was a much cleaner solution since the variables I wanted to pass to my flow were stored in my app as global variables, so much easier to call the flow from different screens.

I'd recommend to anyone struggling with a similar issue to use the blank option to build your flow in power apps rather than using a template.