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
Dyn365CE15 August 2023Use a generic TypeScript to Open Custom Pages
Dyn365CE24 January 2023When your Dataverse Environment doesn’t show up in the maker portal
Dyn365CE9 March 2022Build Deployable Power Automate Flows for Dynamics Customer Voice with Environment Variables
Dyn365CE3 December 2021A Double Expand Query and Some Missing Dynamic Content in Power Automate
