Access a model-driven app view definition in PowerApps
In this topic you open a view definition to display properties and options to configure the view. There are several ways you can access view definitions in PowerApps.
Open a view for editing in the latest view designer
The latest version of the view designer is currently in preview. Some features like advanced filtering, custom controls, and column properties are not yet supported. To accomplish these tasks, Open a view for editing in solution explorer.
Sign in to PowerApps.
“If the Model-driven design mode isn't available, you may need to Create an environment.
Expand Data, select Entities, and then select the entity that you want, such as the Account entity.
Select the Views tab.
Select the view you want to open, such as the account entity All Accounts view.
From the view editor you can perform several tasks:
Open a view for editing from a legacy web app
On any list view for an entity in a legacy web app, on the command bar you will find the following commands after you select the ellipsis (...) button:
View: Opens the definition of the current view in the default solution.
New System View: Opens a new window to create a new view for the current entity in the default solution.
Customize Entity: Takes you to the definition of the current entity in the default solution where you can then select Views.
System Views: Opens the same window as Customize Entity, except with Views selected.
Open a view for editing in solution explorer
Open solution explorer.
Under Components, expand Entities, and then expand the entity you want.
Double-click the view you want to open. This will open the classic view designer.
This list of views has four filters you can use to find the views you want more easily:
All Active Views
Active Public Views
Inactive Public Views
Active System-Defined Views
If the entity that the view is associated with is part of an unmanaged solution, you can still create or edit views for that entity in the default solution. System views are associated with an entity and are not available as separate solution components. Unlike fields, views do not use a customization prefix in a unique name that should be consistent in a solution, so you do not need to create views in the context of a solution.