Splitting data into multiple tables for security purposes and still providing a nice UX to work with business records on a single form. You can achieve both goals with Dataverse and Model-driven Power Apps!
Relational data on Model-driven forms, part 2: Form Component Control
How to make fields from a related table editable on a Power Apps Model-driven app form with the new “forms within forms” PCF control. This second part shows how to go beyond Quick View Forms and create a seamless data entry experience.
Relational data on Model-driven forms, part 1: Main Form Dialog
How to improve the user experience of Power Apps forms that reference data from multiple related tables in Microsoft Dataverse. In the first part we’ll explore the use of Quick View Forms together with Main Form Dialogs.
Unified Interface Form Design Notes
It’s been around a year since Microsoft announced that Dynamics 365 Customer Engagement would be moving from the world of separate web, mobile and Outlook clients into a single Unified Interface (or UCI, as in “Unified Client Infrastructure”). At that time I made a prediction that this level of shift in the client technology would […]
Don’t Merge Your Forms in CRM 2013
If you have been using Dynamics CRM before the 2013 version was released, you may have something in your system called “information forms”. This is not a very descriptive term for them, since of course all the entity forms are about presenting “information” to the end user. These forms actually date back to a time […]
Information Overload: Cleaning Up CRM 2013 Forms
Today I was working on upgrading the customizations of a CRM 2011 org to CRM 2013 forms and restructuring the layouts to fit the new UI. This environment had a custom entity called “Travel Information”, which was used for storing details related to event travel for employees. Here’s what the form looked like when opening […]
