zoukankan      html  css  js  c++  java
  • Entity List with Power Apps on Power Portal

    Use entity lists to display multiple Common Data Service records

    The Entity Lists component allows a maker to display a list of Common Data Service records on a portal webpage by using configuration only. Entity lists are defined by using model-driven app views and can be further configured to filter data based on entity permissions. Entity lists can have additional features enabled such as running workflows and navigating to show detail records.

    Create an entity list

    An entity 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 entity list. Then, the maker will choose the entity and one or more model-driven views to be used to render the entity list on the page.

    Adding entity list in Portal Studio

    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:

    1. The webpage is retrieved.

    2. The webpage will render the entity list based on the Liquid tag that was added when the list component was added to a webpage.

      twig
      {% include 'entity_list' key: '<<Entity List Name>>' %}

    Configure the entity list

    Power Apps portals Studio provides a basic interface for creating and configuring an entity list. Makers can customize all entity list features and properties by using the Portal Management app. To access entity lists in the Portal Management app:

    1. Go to the Power Apps maker portal .

    2. Select the target environment by using the environment selector in the upper-right corner.

    3. From the Apps list, locate and open the Portal Management app (type will be Model-driven).

    4. Select Entity Lists in the left navigation.

    5. Open the list that you previously created in portals Studio.

      List Portal app

    An entity list can be as simple or as complicated as your business requirements specify. The only required properties for the entity list, other than the name and the website, are the target Entity Name and one or more Views.

    Entity 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.

    Entity List structure

    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 Common Data Service entity fields, 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.

    Entity list features

     Note

    Entity lists include the Web Page for Details View and Web Page for Create general properties. These properties are for backward compatibility only. The functionality is included as part of the View Actions and Item Actionsgrid configuration.

    Configuration

    The following sections describe the different types of configuration that are available in entity lists.

    Entity 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 is 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 additional 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 - Records in the list can be filtered on any of the list columns, including ranges, lookups, option sets, and custom FetchXML expressions. Portal users have access to an interactive filtering panel when the entity list is rendered.

    Entity list search and filtering

    Display options

    Views can be rendered as traditional grid lists, a calendar, or a map. Delivering list content as an OData feed is also supported.

    Entity list rendered as map and calendar

    Alternative views might require some additional configuration such as start and end date fields for a calendar or latitude and longitude fields 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 entity list view.

    Actions

    Entity lists can have actions associated with them to enable per list commands, like Create and Download (as a Microsoft Excel spreadsheet), or per record commands like View or Edit, and to trigger workflows.

    Entity list commands

  • 相关阅读:
    “三路九招”打赢电商低成本营销战
    我的文章分类
    ResourceBundle读取中文properties文件问题
    敏捷基础知识
    一个简单方法:构造xml的document,并将其转换为string
    在android源码环境下写上层应用的一个初步解决方法
    Linux 与 unix shell编程指南——学习笔记
    git 分支的基本操作
    使用repo的本地开发流程
    Linux常用命令收集
  • 原文地址:https://www.cnblogs.com/lingdanglfw/p/13967527.html
Copyright © 2011-2022 走看看