I previously showed how you can use Azure Functions and Flow to schedule reports in Dynamics 365. As it turns out, the Azure Function adds unnecessary complexity -- you can instead host the report rendering piece as a plugin/action and call it directly from Flow! You are, of course, constrained by the two-minute execution limit of plugins, but if you run into that you can still use the Azure Function.

If you followed the previous posts, you should have a very basic control that let's you input a number and show it in a specified color if the value is below a threshold. Although the control is functional, it doesn't blend in with the out-of-the-box controls since it doesn't use the same styles. There are three different methods we can use to implement styles on custom controls, and we will explore those in this post.

This post will explore properties for controls built on the Custom Controls Framework. Properties represent values that can be configured, allowing the user to change how the control behaves in order to meet their needs. This post builds on the previous post, so be sure to check that one out first.

Microsoft has been making great strides towards providing the Unified Interface across all devices for Dynamics 365. As part of this Unified Interface, they have implemented the Custom Controls Framework. However, to date, no one has released any developer documentation on how to create custom controls -- the only documentation shows how to use controls provided out-of-the-box. This blog series will show how you can create your very own custom controls!

In the previous post, we created an Azure Function which generates an SSRS report from Dynamics 365. We can now hook that function up to Microsoft Flow as a custom connector, where we can use it as an action in a flow to send the response (i.e. the report file) in an email.