In the past couple of weeks I’ve been using PowerApps, and the overall experience has been great! SharePoint Designer and InfoPath have been replaced by a browser based application that is a lot easier to work with. Of course it is still all very new but the general experience is very good.
Today, I will be looking at Flow. A Flow can be triggered by a lot of things , but for now I will look at a flow that is triggered by a PowerApp.
So If we start with the basics. Adding some tasks. Within Flow there are a lot of tasks available and for Flows related to PowerApps that use SQL Server as their data source I could imagine that there may be a lot of Update row actions in my flows. Flow supports both on-premises and Azure based SQL installations as the “Connect via on-premise (hic) data gateway” indicates.
As with Nintex, Microsoft has now introduced comments for each step
This makes the workflows already a lot easier to understand and compared to SharePoint Designer workflows this is already a massive improvement.
Within Flow it is possible to create variables. So I’m adding a Variables – Initialize variable action to my flow.
Within this action I’m creating a variable State Machine Status
Then I’m adding a Do Until Action
The Do Until action I’m configuring to run until my status variable has been set to Complete.
Then Inside my Do until I create a Switch, which can be found in the … More.
Then by clicking on the + between Case and Default I add all the different states that I want to go through.
Then for each state I’m added a state change:
Time to add the real work into my Flows and my state machine workflow is ready.
Take Our Poll
Have you been using the REST API instead of the create item action in Power…