Portal Advanced Data List widget

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 1 min. de leitura

    • The Portal Advanced List widget shows structured records in an interactive, sortable, and filterable list.

    Nota:
    This widget has limited availability.
    The Portal Advanced List widget presents structured records in an interactive list format, enabling you to sort, filter, and act on the data. The list can also be nested such that you can see the hierarchy of rows.
    Figura 1. Portal Advanced Data List widget when the Nest By column is configured
    Portal Advanced Data List widget displaying a list with the nest by column configured
    Figura 2. Portal Advanced Data List widget with Nest By column not configured
    Portal Advanced Data List widget displaying a list with the nest by column not configured

    Each row in the widget represents a record. You can view, sort, filter and interact with the information presented.

    Nota:
    The widget internally uses the Next Experience components so it’s styled through the Next experience theme (not the Service Portal theme). The following are the steps to style the Portal Advanced Data List widget:
    1. Create a Next Experience theme. For details, see Create a theme with Theme Builder and Create a custom theme by cloning a Theme Builder theme record.
    2. Map the Next Experience theme to the service portal theme used for the portal so that all the widgets that internally use Next Experience components are styled through the mapped theme. For details, see Configure the Portal Advanced Data List widget.
    The Portal Advanced List portal widget can be used in the following scenarios:
    • Static data list: Enables you to display records from tables that you select in the widget instance options. It helps you personalize lists for cases, products, contacts, and more. You can also add buttons and detailed views.
    • Related data list: Enables you to show records linked to the current record on its detail page. To filter them dynamically, use <fieldname={sysID}> in the Filter instance option. The sysID from the URL automatically replaces the {sysID} in the instance.