This past weekend I was in Amsterdam and presented on the differences between classic workflows and flows in Power Automate. It was such a great event, and a subject dear to my heart.
I’m sharing my slides from the session if you would like to get an overview of my conclusions. Ask away if you have any questions!
Additional reading
If you feel like deep diving a bit, here are blog posts of mine that are related to the slides
CDS vs CDS: What Connector should I use in Power Automate?
I see lots of questions regarding the best way to connect to a dynamics environment with Power Automate and people who struggle to find functionality that should be offered but not sure where to look. It’s not clear as crystal that there are two available CDS Connectors in Power Automate and what differs the two.…
Deploy Your CDS Flows Without Updating the Connection
Have you tried to deploy Solutions containing Flows? Do you always spend time on updating the connections in your target environment? You might not have to. Updating Connections The ALM story of Flows still have quite a journey to go. If you’ve ever deployed a solution with Flows you’ve noticed that they are generally turned…
Retrieve Records in N:N relationships with FetchXML and the New CDS Connector in Microsoft Flow
Have you tried to retrieve a list of records in Flow and had to go trough a many to many relationship condition? If you have I can relate to the frustration and complication that task brought. Earlier this week I found a solution – and it was easy, really easy. Let me show you what…
How to Avoid the “Get Record” Action to Retrieve Related Data in Power Automate
In a previous blog post I wrote about how to use FetchXML to List Records from CDS in Power Automate. But what if a column you defined in your FetchXML doesn’t show up in the Dynamic content because it is a column from a related record? Defining the FetchXML Let’s start with using the most…
Be Lazy: Filter List Records in Power Automate with FetchXML Builder
If you navigate to the classic workflow designer you’ve probably seen the recommendation to use Microsoft Flow for background workflows. Although we’re not completely there yet with parity between the two – Power Automate is the way forward. Without mentioning all the differences between Flows and Classic Workflows, Power Automate has one HUGE advantage: List…
Sara Lagerquist 
Reblogged this on Dynamics CRM Experience.
LikeLike
Thx for sharing the information good stiff to know when starting with Power Automate.
In a different post of someone else (forgot the name) about working with child flows, it was said to start the child flow with a Http trigger request. Whats the difference to your recommendation to start with a power trigger?
LikeLike
Hi!
Yes you are right, there are actually 3 triggers that you can use, I only showed the powerapps one 🙂 You can read about all three here: https://docs.microsoft.com/en-us/power-platform-release-plan/2019wave2/power-automate/call-child-flows
LikeLike
Hi. Your slides are helpful but, in some cases, missing context / explanation. Is there a recording of you presenting this posted somewhere so that I can better understand the material?
LikeLike
Hello!
Unfortunately there is no recording. Is there any slide in particular you would like me to explain I’m happy to do so even though it was a while ago that I did the slides 🙂
LikeLike
Thanks! I’m new to this and your blog is definitely getting bookmarked!
LikeLike
Thank you, that’s is great to hear!
LikeLike