You have to toggle reset back to false after you toggle it on with true. The momentary setting to true will run the timer. It wont run the second time if you dont turn it back to false.
Set( wait, true ); ClearCollect( WHFilterResults, FilterTest.Run(0) ); Set( wait, !true ); Navigate( BrowseScreen, None )
That's an example from a PA I have. This is tied ot a Button OnSelect, which then triggers a Flow to filter a Sharepoint document library and create a collection from it. By setting the "wait" variable to true, then setting it false after the collection gets created, it delays the Navigate accordingly. This then, takes the user to the BrowseScreen only after contents are populated there.
An alternative to using timers is having the flow return something to the PowerApp. This way, the app will call your flow and wait until a result is returned before proceeding to the next operation.
Inside your flow, use either the Response or Respond to PowerApp actions.
Hope that helps.
I had a similar situation, so I updated my flow to send a response back to the PowerApp either Success / Error in my case...
Then I loaded the Flow Response into a variable, Global or Context and had an If / Switch statement updates my user screen/navigation based on the results of the response.
Read the announcement for more information!
Congrats to the finalists of our ‘Better Together’-themed T-shirt design contest! Click for the top entries.
Features releasing from October 2019 through March 2020
Innovate, Collaborate, Grow - The top training and networking event across the globe for Microsoft Business Applications