Power Automate Field Guide
The Power Automate Field Guide is a collection of short training topics covering real-world challenges you will encounter when building Power Automate automations. Unlike most of our courses this one will be incrementally built over time as you suggest topics we should cover.
COURSE INSTRUCTORS
David Yack
David is the CTO of Colorado Technology Consultants based in Colorado and is recognized as a Microsoft MVP
George Doubinski
Microsoft MVP. Architect. Coder. Author. Blogger. Speaker. Trainer. Specialist in all things difficult.
Course Module Details
Overview (2 Minutes)
-
Watch this first and learn how this course works and how to add your ideas to our content request list and vote for ideas.
Microsoft Office 365 (0.5 Hours)
In this module we focus on using Power Automate with Microsoft Office 365. Learn how to use the Office 365 connectors and service capabilities to build automations.
-
Handling Inbound Email Preview
In this video we look at how to handle automation of inbound e-mails. This includes looking at using Exchange shared mailboxes and Microsoft Dataverse queues. We compare and contrast approaches to help you decide the right approach for your needs. If you ever wanted to automate your own inbound e-mail processing this is a must watch.
General (1.5 Hours)
-
In this video we look at using Power Automate to generate test data. We will cover inline data, randomizing data and more.
-
Search, followed by an optional record creation if target is not found, is a very common sequence in Power Automate flows connecting to Dataverse. In this video you will learn how, by using child flows, create robust and intelligent universal search and create flow blocks.
-
Dataverse has very extensive metadata available via Web API but Dataverse connector in Power Automate does not provide access to this information. Where it can be used? Have you ever tried to set the value of a choice / option set / picklist column using the label instead of the underlying number value in Power Automate? You can set the value in a flow using either a static value from a dropdown or provide the underlying number value of the choice. If the input value for the choice is provided as text, how do you work out the underlying number value of the choice? For small choices / option sets / picklists e.g. Yes, No, Maybe then a Switch action works great. But what if your choices / option sets / picklists contains 20+ possible values? You will need several monitors side-by-side just to fit it all horizontally. And maintaining this flow becomes a challenge. This is exactly where metadata can help. It's also useful for accessing the information into any of the installed languages, working out data ranges and other properties, and many more. In this video you will learn how to access the Dataverse metadata in Power Automate and how to make the most out of it.