Model-driven forms are a vital part of the Microsoft Power platform and are essentially a form designer that you use to build your apps. In a model-driven form, the layout is responsive and dictated by the components you add to the form, the platform then adjusts the layout to provide the best viewing experience, whether on a desktop, tablet, or phone.
Model-driven forms are fundamentally categorized into three types:
- Main Form: This is the primary form you see when you open a record. These forms give the most information and include multi-tab and multi-column structure. You have access to insert numerous types of controls including text boxes, drop-down lists, date pickers, and others.
- Quick Create Form: This form is a more streamlined version of the main form where users can create new records without leaving the page they’re currently on. You’ll set this up as a light box overlaying the existing form.
- Quick View Form: A Quick View form allows users to see related information without navigating away from the current form. This type is not editable but very useful for related lookup information.
Form Type | Description |
---|---|
Main Form | This is the primary form which provides detailed information of a record |
Quick Create Form | A simplified version of the main form for quick entry |
Quick View Form | Read-only form to view related record information |
Each form type can be customized according to the business requirements. The model-driven forms allow insertion of various controls, sections, tabs, charts, and grids, making it versatile. The following is a simple code snippet example illustrating how to navigate to a main form:
// Below is an example to open the main form of an Account record
Xrm.Navigation.openForm({entityName: "account", entityId: "GUID_OF_The_RECORD"});
Dataverse Views
Moving onto Dataverse views, they are visuals that allow you to view and analyze your data more naturally and efficiently. Dataverse views are custom views you create on top of your data. It primarily serves two purposes:
- Filter and Display Data: You can specify criteria that determine which records will appear in the view. You can also select which columns to be displayed and in what order.
- Sorting of Data: In views, you can define the sorting order of data either in ascending or descending order.
There are two primary types of views:
- Public Views: These are available to all users.
- Personal Views: These views are created by individual users for their use but can be shared with others.
View Type | Description |
---|---|
Public View | Available to all users |
Personal View | Created by individual users for personal use |
Creating a Dataverse view involves defining the columns that should be in the view and then setting the filter criteria. You can also configure advanced sorting options. Here’s an example of creating a view on the ‘accounts’ table and specifying the columns and filter criteria:
// Initialize a query object
QueryExpression query = new QueryExpression("account");
// Define the columns for the query
query.ColumnSet = new ColumnSet("name", "address1_city", "emailaddress1");
// Define filter criteria
query.Criteria = new FilterExpression();
query.Criteria.FilterOperator = LogicalOperator.Or;
query.Criteria.AddCondition("address1_city", ConditionOperator.Equal, "Seattle"); query.Criteria.AddCondition("address1_city", ConditionOperator.Equal, "Redmond");
//Execute the query to get the view
RetrieveMultipleRequest retrieveRequest = new RetrieveMultipleRequest { Query = query };
RetrieveMultipleResponse retrieveResponse = (RetrieveMultipleResponse)crmService.Execute(retrieveRequest);
To summarize, understanding Model-Driven Forms and Dataverse Views are crucial to become an efficient Power Platform App Maker. Model-Driven Forms helps in designing user-friendly interfaces, whereas Dataverse Views help in analyzing the data efficiently. These features are essential and commonly used in Power Platform, so understanding and practicing them will help you pass the PL-100 Microsoft Power Platform App Maker exam assuredly.
Practice Test
True or False: Model-driven forms in Microsoft Power Platform utilize the data from Dataverse views to model data.
- True
- False
Answer: True
Explanation: Model-driven forms, as the name suggests, are driven by data models. Dataverse provides a secure and scalable data service that these forms utilize.
Multiple Select: What are some of the key features of model-driven forms in Microsoft Power Platform?
- a) Driven by data models
- b) Highly customizable
- c) Automatically responsive
- d) Limited to certain data types
Answer: a, b, c
Explanation: Model-driven forms in Power Platform are designed to be driven by data models, highly customizable and automatically responsive, with no limitations on data types.
True or False: Dataverse views in Microsoft Power Platform can’t be customized to suit specific business needs.
- True
- False
Answer: False
Explanation: Dataverse views in Power Platform are highly customizable, allowing businesses to tailor views to suit their specific needs and scenarios.
Single Select: Which of the following best describes a Dataverse view?
- a) A pre-built form in Power Platform
- b) A customizable view of data in Power Platform
- c) A set of pre-built triggers and actions in Power Automate
- d) A visual representation of Power BI data
Answer: b
Explanation: Dataverse views provide a customizable view of data in Microsoft Power Platform.
True or False: Model-driven forms and Dataverse views in Microsoft Power Platform can be used independently.
- True
- False
Answer: True
Explanation: Although they are often used in combination to create powerful applications, model-driven forms, and Dataverse views can be used independently in Power Platform.
Multiple Select: What are some of the uses of Dataverse views in Power Platform?
- a) Customizing the view of data
- b) Defining business rules
- c) Managing security roles
- d) Creating data-driven apps
Answer: a, d
Explanation: Dataverse views in Power Platform are used for customizing the view of data and creating data-driven apps.
True or False: Model-driven forms in Power Platform can only display data from a single entity.
- True
- False
Answer: False
Explanation: Model-driven forms can show data from multiple entities in Microsoft Power Platform.
Multiple Select: What can be displayed by model-driven forms in Power Platform?
- a) Data from a single entity
- b) Data from multiple entities
- c) Related records from associated entities
- d) Unrelated records from other entities
Answer: b, c
Explanation: Model-driven forms in Power Platform can present data from multiple entities and related records from associated entities.
Single Select: What plays a underlying foundational role in Power Apps?
- a) Logic Apps
- b) Power BI
- c) Dataverse
- d) Power Automate
Answer: c
Explanation: Dataverse plays a crucial role in Power Apps as it provides a secure and scalable data service and storage.
True or False: The Microsoft Power Platform App Maker can’t make use of Dataverse views to display data.
- True
- False
Answer: False
Explanation: The Power Platform App Maker can use Dataverse views to display and manipulate data in a variety of ways.
Interview Questions
What is the main idea behind model-driven forms in Power Platform?
Model-driven forms on Power Platform provide a structured UI that is directly linked to a data source. It allows automation and visualization of data without writing code.
How many types of model-driven forms does the Power Platform support?
Power Platform supports three types of model-driven forms: Main, Quick Create, and Card.
What is the role of Main forms in the Power Platform?
Main forms provide the primary interface for interacting with data in a model-driven app. These forms contain data, controls, and tabs used to model the data and its functionality.
Can you explain what Quick Create forms are in Power Platform?
Quick Create forms are forms that pop up when a user chooses to create a new record from the global navigation bar or from a lookup field within another form. They allow for quick and easy data entry.
What function does a Card form serve in Power Platform?
Card forms are used in Power Platform to display data from a single record in a Summary or Reference Panel, providing a quick overview of relevant information.
What is the Dataverse in Microsoft Power Platform?
Dataverse is a data service that acts as a robust storage and management platform for business data in Power Platform.
Are views in the Dataverse customizable?
Yes, views in the Dataverse are customizable. They can be modified to filter, sort, and display data in a way that meets the needs of a specific role or task.
How many types of views are there in Dataverse?
There are four types of views in Dataverse – Public, System, Personal, and Quick Find.
What is a Public view in Dataverse?
A Public view in Dataverse is a predefined set of filters and sorting operations applied to a table, which is available to everyone who has access to the particular table.
What is a Personal view in Dataverse?
A Personal view is a saved set of query conditions, sort orders, and display settings that a user can define and save for repeated use. They are visible only to the user who created them.
What is a System view in Dataverse?
System views are views which are pre-defined by Microsoft and cannot be deleted or renamed. They are essential for system functions and features.
What role does a Quick Find view play in Dataverse?
Quick Find views are used to perform a search on selected fields within a table. They define the set of attributes that are displayed in lookup dialog boxes and search results.
What components make up a model-driven form in Power Platform?
Model-driven forms in Power Platform consist of several components like controls (e.g. text fields, buttons), tabs, sections, and subgrids, each serving its own function for data management.
How can Dataverse views be used within Power Platform applications?
Dataverse views are utilized by Power Platform applications to present data in a structured and organized way, making it accessible and understandable for users to interact with them.
What security permissions are required to customize a model-driven form or a Dataverse view?
To customise a model-drive form or Dataverse view, users need the appropriate security role with permissions to read and write metadata and data in the tables that the form or view is built on.