When you develop PowerApps you will quite quickly find that you can start your flow directly from your PowerApp. But is this the best way? Or is this the only way?
I’m going to start simple by creating a clickable icon in PowerApps. In my case this is just a Add icon.
Then within my Flow I added the dynamic data “Ask in PowerApps” and added two PowerApps variables:
Then on my + icon I set the my variable data that I want to use within my flow
And after one failed attempt my Flow ran successfully.
Ok, this is great we can start a flow directly from an app, but we have to be careful.
Quite often you might want to run a flow after the update of some data. Although it is perfectly possible to start my flows as part for the saving a piece of data it might be safer to start the flow once the data has been stored. Yes, you could probably handle this in PowerApps, but when storing data in SharePoint list items, I would consider creating the flow that triggers on the list items creation or modification.
There are of course always reasons why you would want a manual start of a flow. For example flows that are not immediate triggered by a data update. Or if you wanted to avoid the automatic starting of a flow. As we have seen in one of my previous posts it can be difficult to handle the automatic starting of flows if your flow includes updates of the triggering data.
Discover more from SharePains
Subscribe to get the latest posts sent to your email.
Pieter Veenstra
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like. I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide. For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions. You can contact me using contact@sharepains.com