Understand model-driven app views
Model-driven apps use views to define how a list of rows for a specific table are displayed in the application.
A view defines:
- The columns to display.
- The order of the columns.
- How wide each column should be.
- How the list of rows should be sorted by default.
- The default filters applied to restrict the rows that will appear.
Once a view has been made available in the app, the user can select it.
When designing an app, the maker decides which of the public views to make available to app users. These decisions are typically based on the type of user, such as sales or marketing, that will use the app.
Views can be developed through the table designer or the app designer.
Types of views
There are three types of views: personal, system, and public.
- Personal view - Personal views are owned by individuals and only visible to that person unless they share their personal views with others.
- System view - As a system administrator or system customizer, you can edit system views. System views are special views the application depends on, which exist for system tables or are automatically created when you create custom tables. These views have specific purposes and some additional capabilities.
- Public view - Public views are general purpose views that you can customize as you see fit. They are important because all app users can access them, when they are made available, by using the view selector. It is possible to use public views in subgrids in a form or as a list in a dashboard.
Views within model-driven apps
Users may want to view data in relation to a table in a range of ways. A drop-down list of views is frequently displayed in the application so these can be selected.
Personal views are included above the list of system or public views that are available in the app. This makes it easier for users to find the data that is important to them.
The rows that are visible in views are displayed in a list. Views frequently provide options for users to change the default sorting, column widths, and filters to more easily find the data that's important to them.
Views are not only used by users within model-driven apps, they can also be used to define the data source in, for example, charts that are used in the application.
Personal views can be created by following these steps:
- Select Create view from the command bar in your model-driven app.
- Define the view filters.
- Then select Save.
While you can create a new personal view based on a system or public view, you can't create a system or public view based on a personal view.
Personal views can be created by users who have at least User level access to actions for the Saved View table.
As system administrator, you can modify the access level for each action in the security role to control the depth to which people can create, read, write, delete, assign, or share personal views.
|Quick Find||The default view used when searches are performed using Quick Find. This view also defines which columns are searched when using search capabilities of Quick Find and Lookup views.|
|Advanced Find||The default view used to display results when using Advanced Find. This view also defines the columns used by default when new custom public views or personal views are created without defining a view to use as a template.|
|Associated||The default view that lists the related tables for a row.|
|Lookup||The view that is displayed when you select a row to set for a lookup column.|
These views are not shown in the view selector and you can't use them in sublists in a form or as a list in a dashboard. You can't delete or deactivate these views. For more information about removing views, go to Remove views.
System views are owned by the organization so that everyone can view them. For example, everyone has organization-level access to read rows for the view (
savedquery) table. These views are associated with specific tables and are visible within the solution explorer. You can include these views in solutions because they are associated with the table.
System views are cached for performance optimization purposes and therefore plugins on the
savedquery table aren't supported.
Some public views exist by default for system tables and for any custom table. For example, when you create a new custom table, it will have the following combination of public and system views.
|Active table plural name||Public|
|Inactive table plural name||Public|
|Quick Find Active table plural name||Quick Find|
|Table name Advanced Find View||Advanced Find|
|Table name Associated View||Associated|
|Table name Lookup View||Lookup|
You can create custom public views. You can delete any custom public views you create in an unmanaged solution.
You can't delete any system-defined public views.
Custom public views added by a managed solution should only be deleted by uninstalling or updating the managed solution.
How to access the view editor to create or edit views
- App Designer: If you're working in an app, you may want to use the app designer, which provides a simple and intuitive user interface with drag-and-drop capabilities for creating views. More information: Tutorial: Create and edit public or system views by using the app designer
- Solution explorer: If you're already experienced with Dynamics 365, you may want to use the solution explorer. For more information, go to Navigate to advanced app making and customization areas
As a system customizer you can customize the views through controls by making grids (lists) editable.
The following controls are used:
- Editable grid: Allows users to do rich in-line editing directly from grids and subgrids whether they're using a web app, tablet, or phone. For more information, go to Make grids editable using the Editable Grid custom control
- Read only grid: Provides users an optimal viewing and interaction experience for any screen size or orientation such as mobiles and tablets by using responsive design principles. For more information, go to Specify properties for Unified Interface apps
Submit and view feedback for