From the course: Microsoft Power Platform Functional Consultant Associate (PL-200) Cert Prep
Model-driven apps: Creating forms
From the course: Microsoft Power Platform Functional Consultant Associate (PL-200) Cert Prep
Model-driven apps: Creating forms
- Now that we've got our data model down, we need a way for users to interact with it. This chapter will explore the no-code, low-code types of apps we can build based on our Dataverse data model. Power apps, whether that's model driven or canvas type and power pages. We'll start off by looking at creating forms. One of the key components in model-driven apps. Model-driven forms are a way to display, and edit detailed data for a dataverse row. It's how a user will interact with the data in the row when using the app. In this example, we'll look at a form for the contact dataverse table. You can begin with either the app designer or the Dataverse table to create or edit a new form. Either way, you'll be taken to the form designer, which allows you to drag and drop columns and components into sections on your screen to fill out the form. Form are made up of a header, a body and footer. You can place columns in any of these areas. The body can contain different tabs, and sections to logically group your data for the user. Like you can see here, the summary tab contains sections with contact information and address, and the details tab contains personal information. You can drag and drop sections into the form. We'll add in a one-column section here, then add in the columns you wish to display. So let's take the address and drag that in. You can reorder columns as you need, and even change some settings such as making the field read-only or renaming the label. Once you've finished editing or creating the form, remember to click save and publish. This will make sure that your changes are visible to users. Here's what this form would now look like for the user of the model-driven app. There are four types of forms that you can configure for a Dataverse table. Main. Quick view. Quick create. Card. Main forms are the primary user interface where people view and interact with their data. You can assign security roles to these forms. A quick view form control can be added to a main form displaying information from a related table row. You can't edit directly from the form, and they don't support scripts. Quick create forms enable a streamlined data entry experience with support for form scripts and business rules. They appear when creating a new record from a lookup or a subgrid. Card forms are used to present data in a compact format suitable for mobile devices, and are additive views using the read-only grid control. These are the basics you need to know for building forms in model-driven apps. There are also specialized form components that you can add in. We'll look at these next.
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
-
Model-driven apps: Creating forms3m 8s
-
(Locked)
Model-driven apps: Specialized form components2m 4s
-
(Locked)
Model-driven apps: Creating views2m 53s
-
(Locked)
Model-driven apps: Reporting options2m 24s
-
(Locked)
Model-driven apps: Creating site maps1m 57s
-
(Locked)
Model-driven apps: Sharing the app2m 57s
-
(Locked)
Model-driven apps: Custom pages1m 49s
-
(Locked)
Model-driven apps: Business rules3m 2s
-
(Locked)
Model-driven apps: Modern commands2m 45s
-
(Locked)
Canvas apps: Use cases2m 21s
-
(Locked)
Canvas apps: App structure2m 44s
-
(Locked)
Canvas apps: Formulas, variables, and collections3m 40s
-
(Locked)
Canvas apps: Running Power Automate flows3m 44s
-
(Locked)
Power Pages: Overview, templates, and use cases3m 7s
-
(Locked)
Power Pages: Configuring pages, forms, and navigation4m 10s
-
(Locked)
Power Pages: Security3m 25s
-
(Locked)
Power Pages: Registration options1m 41s
-
-
-
-
-
-