In Power Apps Model Driven Apps, VIEWS are used to show rows for a specific table. A view is defined by the following:
- The columns (attributes) to display
- The width of the columns
- How the rows are sorted by default
- Which filters are applied to determine which rows appear in the list by default
Below is a diagram with the available views including a cheatsheet on how to configure them.
When best to use this cheatsheet?
- To deliver a quick training on available views in Power Apps.
- To make sure you map requirements to out of the box features and not build something custom.
- A quick reminder of the out the box features when designing solutions.
References:
- Microsoft Docs: Understand model-driven app views
- Tip #1211: Mixing entities to build complex views
- PCF Gallery
- Amey Holden: For pointing me in the right direction about the PreviewGalleryControl
Awesome, Thanks for this insights!
Btw, any cheat sheet for when you’re embed canvas app into model-driven forms ?
I found some limitation like : you actually need a record first in order to load canvas app – cannot create new record by using the embed canvas app it self, the height of canvas app always reducing in scale with the width of the screen – this is not good when we display it like the phone size and portrait whereby the width is small but the height is long, because currently, it is following the width shrinking, so the height shrinking as well. Another is can we make use and control the standard toolbar, buttons of model driven for the canvas app – so we can do some addition logic in their save / save & close / back button. Thanks