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
#Dyn365CE2019.12.02MVP Advent Calendar: Transport Data Between Environments with Sara’s Favorite Tool!
#Dyn365CE2019.11.25How to Avoid the “Get Record” Action to Retrieve Related Data in Power Automate
#Dyn365CE2019.11.13Be Lazy: Filter List Records in Power Automate with FetchXML Builder
#Dyn365CE2019.09.18Retrieve Records in N:N relationships with FetchXML and the New CDS Connector in Microsoft Flow
