How to bring external data from SQL Server tables into your Model-driven Power Apps with the new Virtual Connector Provider. This blog posts demonstrates how you can transparently combine the virtual & physical data onto a single screen for the users to work on.
One-to-one relationships and forms within forms
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!
Making Model-driven Power Apps visible (and hidden)
Managing end user access to Model-driven apps isn’t as straightforward as with Canvas apps. Here’s how the list of Power Apps actually works and what the “share” feature does & doesn’t do for Model-driven app.
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.
