Use table lists to display multiple Microsoft Dataverse records
The List component allows a maker to display a list of Microsoft Dataverse rows on a portal webpage by using configuration only. Lists are defined by using model-driven app views and can be further configured to filter data based on table permissions. Lists can have more features enabled such as running workflows and navigating to show detail rows.
Create a list
A list can be added as a component to a webpage in Power Apps portals Studio. After placing the list component on a page, the maker will need to set the properties of the list. Then, the maker will choose the table and one or more model-driven views to be used to render the list on the page.
List rendering
Adding a list component in portals Studio will add the corresponding Liquid tag to the webpage content.
When the webpage is requested, the list rendering process is as follows:
The webpage is retrieved.
The webpage will render the list based on the Liquid tag that was added when the list component was added to a webpage.
{% include 'entity_list' key: '<<List Name>>' %}
Configure the list
Power Apps portals Studio provides a modern interface for creating and configuring a list. Makers can perform the following tasks:
- Define name, table, and views for the list.
- Enable create, view, edit, and delete operations on the table rows and define how they implemented (form, webpage, or URL).
- Change the page size.
- Enable search within the list.
In addition to the above, makers can customize all list features and properties by using the Portal Management app. To access lists in the Portal Management app:
Sign in to the Power Apps maker portal.
Select the target environment by using the environment selector in the upper-right corner.
From the Apps list, locate and open the Portal Management app (type will be Model-driven).
Select Lists in the left navigation.
Open the list that you previously created in portals Studio.
A list can be as simple or as complicated as your business requirements specify. The only required properties for the list, other than the name and the website, are the target Table Name and one or more Views.
Lists are highly configurable and have many settings that define the list behavior. Lists can also include actions for the user to interact with the items on the list.
The following sections explain some of the most common features and settings.
Note
Most of the options that add interactive elements, such as buttons, support customization of the elements in multiple languages. For example, if multiple views are enabled, the name for each of the views in the view selector can be customized for each of the enabled portal languages.
Views
Selected view(s) define the Dataverse table columns, list layout, and the default sort order.
Multiple views - If more than one view has been specified, a drop-down list will be rendered to allow the user to switch between the views.
Sorting and pagination - Sorting is enabled on any of the displayed columns and the page size is configurable.
Configuration
The following sections describe the different types of configuration that are available in lists.
Filter and search
Lists provide you with several options to filter and search list data:
Search - When quick search is enabled, the portal will render a text search box. It's similar to the quick search feature in model-driven apps. Quick search runs across the view columns and allows you to locate the information within the larger lists by using plain text input. Portal users can use the asterisk wildcard character to search on partial text.
Portal filters - The list data can be filtered by the current portal user, the current portal user's parent account, and the current portal website. This feature enables some common scenarios without needing more configuration:
- List of product reviews that are left by the current user
- List of campus buildings for the current user's department (account)
- List of all draft pages for the current website, only when multiple portals are provisioned
If the current portal user and current portal user's parent account filters are enabled, the portal will render a drop-down list to allow the user to view their own data (My) or their parent account's data (account name will be displayed).
Metadata filters - Rows in the list can be filtered on any of the list columns, including ranges, lookups, choice(s) columns values, and custom FetchXML expressions. Portal users have access to an interactive filtering panel when the list is rendered.
Display options
Views can be rendered as traditional grid lists, a calendar, or a map.
Alternative views might require some other configuration such as start and end date columns for a calendar or latitude and longitude columns for a map.
Important
Map and calendar views require page templates that can render the view. When a starter portal is provisioned, Rewrite page templates like Page or Full Page support this functionality. Pages that use web templates will render the default list view.
Actions
Lists can have actions associated with them to enable per list commands, like Create and Download (as a Microsoft Excel spreadsheet), or per row commands like View or Edit, and to trigger workflows.
For more information, see About lists.
Watch the following video to learn how to configure and display the view on a portal page and add interactive filtering capabilities on an existing Dataverse table.
Now that you've observed how the lists are built and rendered, you can learn how portals can display and interact with individual rows.
Потрібна допомога? Перегляньте наш посібник із виправлення неполадок або повідомте про конкретну проблему.






