In Part 1, I introduced Dialog Boxes and showed the basics of how to create one and import it through a solution. In this post, we'll take a look at a few other features including passing data parameters into the dialog and adding event handlers on form load or on click of a button.
Back in July 2017, Microsoft deprecated the dialog process, and announced that they would be replaced with task flows. While I think task flows are great, they only let you interact with fields on a single entity. If you want to do something more advanced like working with fields from multiple entities or interfacing with data from an external web service, you cannot. However, there is a new Dialog Box component in the system that we can use!
With the new Unified Interface apps for Dynamics 365, it is now possible to "log in" as another user. This will be a major benefit to administrators/customizers as they troubleshoot issues on behalf of their users. The reason this is possible is because most (all?) of the data interactions in Unified Interface apps are done through the API, and the API supports user impersonation!
Microsoft occasionally deploys updates to Dynamics 365 without notice. This is considered unplanned maintenance and they do it to fix critical bugs and patch security holes. Using the Version Monitor solution, you can create a Flow to notify you whenever the version number has changed!
I've posted a few blogs so far about the Custom Controls Framework. If you haven't seen them, you can check them out here. Here are a few other random thoughts on unbound controls, further exploration, and some open questions I have.