Following on from yesterday’s post about Input and Output Parameters in Power Automate, today I’m looking at the same for flows that are called from a Power Apps canvas app. We will find that child flows and flows called from an app are very different.
Author: Pieter Veenstra
Business Applications Microsoft MVP working as the Head of Power Platform at Vantage 365. You can contact me using contact@sharepains.com
In this post, I will look at the input and output parameter types for child flows. Recently I hit a couple of small issues with the various data types that are worth sharing.
It’s time to have a look at some of my older posts. In this post I’m going to have another look at these Power Automate ideas. Back in 2017/2018 when Power Automate was still called Microsoft Flow, I wrote 100s of posts about developing flows.
How many of these ideas do you still use now?
If you have worked with the Excel Online connector in Power Automate then you will most likely know the pains of this connector. In this post I’m giving an easy way to replace the connector with the much more reliable Microsoft Graph API alternative.
A while back I wrote an introduction post about automated testing Power Apps using Power Automate Desktop. Today, I’m going to look at automated testing in more detail focussing on the various controls available.
Load More