Microsoft recently added functionality for one-click document generation to Dynamics 365. Although this is great functionality, it is a bit limited with regard to where it can save the generated document. Out of the box, we can add the SetWordTemplate action to a workflow, but that generates the document and saves it as an attachment to an annotation. What if you want to save it in SharePoint? We can accomplish this with a custom plugin.
Here's a quick tip to make working with the Dynamics 365 Web API in Postman even easier. Working with the Web API requires an Access Token which takes several steps to retrieve, and since the tokens expire every hour, it can be a little frustrating. By using a Pre-Request Script, you can have Postman automatically retrieve Access Tokens for you and refresh them when they expire.
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!