As part of the controls that are available for Model Driven apps in unified interface we have the Option Set PCF custom control. Recently I encountered a weird behavior in these controls. I am not sure whether Microsoft would consider this as a bug or a feature, but I wanted to discuss this here, so that possibly it can help other who are encountering the same issue.
We have all seen different articles and posts that detail the steps of how to embed a Canvas App within a Model-Driven form by adding the Canvas App control to a field on the form, but sometimes that might not be enough for the requirements that we have in place.
With the release of Microsoft Dynamics 365 and Power Platform 2020 Release Wave 2, Microsoft has made several enhancements related to the email experience in model-driven apps. This post will cover the email file attachment enhancements as well as the new experience for email templates.
With the release of Microsoft Dynamics 365 and Power Platform 2020 Release Wave 2, Microsoft has made some enhancements to the document generation capabilities and file attachments in model-driven apps. This first post will cover the document generation capabilities and the generation of pdf documents based on document templates.
Today, July 8, 2020, Microsoft released the Power Platform and Microsoft Dynamics 365 2020 Release Wave 2 plan documentation with a list of all the features that will be made available in the Wave 2 timeframe which starts October 2020 until March 2021. Going through all of the features is almost impossible unless you want a few hundred pages of documentation.
When working with model driven apps, we have the ability to navigate through the flow of the record using the Business Process Flow. The BPF is a great way to navigate through the different stages of the record, but what if that is just not enough. What if in order to complete the record I have to go through 10 or maybe more stages.
Over the past couple of years, since the release of Unified interface, one of the biggest pain points for most customer was that features that are available in the web client are not available in the new Unified Interface. There were a lot of improvements in the Unified Interface with the responsive client, custom controls and more, but when you are used to working in a certain way, taking away features is sometimes hard to get used to.
On one of our recent projects, we had a requirement to only allow valid Tax Id Numbers on that field. There are various ways of implementing this, but as the direction seems to be to shift the development of these kind of features to custom controls, we decided to implement it as a PCF custom control.
In many of the projects that I have worked over the past years, either government of private sector, while working with other businesses it has become a common practice to request that Industry information from the companies that you work with, and furthermore the NAICS code. While not every company knows their NAICS code, drilling down to get it using the Industry (2-digit code), Subsector (4-digit code) and NAICS title (6-digit code) might be the way to go, sometimes you might want to bypass this complex search if you know ahead of time your business’ NAICS code and have it auto populated for you.
As part of the October 2019 release (Wave 2), the Unified Interface will receive a few usability enhancements that will address some of the issues that were reported by the community. These enhancements include:Â Anchoring error notifications, Viewing inline images for emails that are read-only, Improved usability/density and filtering in views and form header usability enhancements.
