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 Records. Something…
Continue Reading Sara Lagerquist’s Article on their blog
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…
Blog Syndicated with Sara Lagerquist’s Permission
More About This Author
Array
Dyn365CE2021.09.21How to create in-app Notifications with Navigation in Model-driven Apps with Power Automate
Dyn365CE2020.09.03Get EntitySetName with XrmToolBox
Dyn365CE2020.06.16Get App ID with List Records in Power Automate
Dyn365CE2020.03.19Child flows in Power Automate Compared to Child Workflows
