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!
What will Power Fx mean for Model-driven Power Apps?
Will the common low-code programming language turn business app customization from GUI based tasks to a jungle of formulas, or will we just gain new powers?
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 […]
Card Forms and List Views in Unified Interface
Since the beginning of time, meaning early days of MS CRM, we’ve grown accustomed to the fact that record fields in Dynamics 365 Customer Engagement can be presented either via entity forms or entity views. The entity form shows the editable fields of a single record, whereas the entity view gives us a list of […]
