A table contains a set of line items, each displayed as a row that’s divided into columns. Line items can contain data of any kind, but also interactive controls, for example, for editing the data, navigating, or triggering actions relating to the line item.

To display data in tabular form, several table controls are provided. They belong to two groups that each share a consistent feature set:

• Fully responsive tables are the responsive table, list, and tree.

Do not use responsive tables to display more than 200 rows after filtering. Use the grid table instead. Note that the 200-row limit does not apply to the database table, which can contain thousands of rows.

• Desktop-centric tables are the analytical table, grid table, and tree table. They are not fully responsive. The grid table is optimized for handling a large number of rows.

Usage

Use the responsive table if:

• You need a table to display a moderate amount of data. When your data is of average complexity, the responsive table can handle up to 200 items. However, if your data is more complex, the limit is lower. For less complex data, it is higher. Note that this number doesn’t refer to the number of items in the database or in the filtered results, but the volume actually loaded at any point. Factors influencing the exact limit include:
  • The number of loaded rows in the table
  • The number of displayed columns
  • The complexity of the cell content (for example, simple text vs. complex charts)
  • Other elements on the page (for example, multiple pages in a flexible column layout, or several tables/elements with more complex rendering on the page)
  • The browser used

  For loading large amounts of complex data, use a grid table instead, as it can handle higher volumes more efficiently.

• The table content should be flexible and visually appealing. The responsive table offers the most flexibility for its content because all SAPUI5 controls, and even multiple controls, can be used. In addition, different rows can be based on different item templates.
• The users focus on line items, not on individual cells.
• A main use case involves selecting one or more items, and users need details to select them correctly.
• Line items are independent of each other and no operation across columns is needed.
• You want to have only one implementation for all devices. Make sure you adapt the responsive table design to offer the best solution for mobile devices.

For more information, see the responsive table control.

Use the list if:

• You want to display a simple dataset.
• A table would be too complex.
• A list of actions is to be displayed.
• Simple two-level hierarchies are required (by using grouping or navigation).
• The main use case involves selecting one of several items based on only a few details.
• You require a list for a list-detail scenario using the flexible column layout.

For more information, see the list control.

Use the tree if:

• You want to display a simple hierarchical dataset.
• You want to use a hierarchical list for a list-detail scenario using the flexible column layout.
• Using a tree table would be too complex.
• The main use case involves selecting one of several hierarchical items based on only a few details.

For more information, see the tree control.

Use the grid table if:

• You need a table to display large amounts of data because the grid table can handle higher volumes more efficiently.
• The cell level and the spatial relationship between cells are more important than the line item, such as if users need to recognize patterns in the data, like in waterfall charts.
• Comparing items is a major use case. The grid table layout remains stable irrespective of the screen width. In addition, a cell only ever contains one control.
• The sequence of the items in the table is important.
• Your use case is for tasks performed on desktop and tablet devices.

For more information, see the grid table.

Use the tree table if:

• Data needs to be displayed in a hierarchical manner.

For more information see the tree table.

Use the analytical table if:

• You need multilevel grouping as well as grand totals and subtotals.

For more information, see the analytical table.

Responsiveness

Fully Responsive Tables

The fully responsive tables adjust their appearance to the to the screen size so you can use it on all devices.

Make sure you design the best responsive table solution for the tasks performed on each device type. Sometimes, a solution without a table is more useful and useable for mobile devices.

Desktop-Centric Tables

The desktop-centric tables are not fully responsive, but available for only desktops and tablets, and they support touch interactions.

For mobile use cases, you need to:​

• Create a new Fiori application with reduced complexity, not an exact match of the desktop application.​
• With the new application, address the most important use cases for users in a mobile context. The responsive controls (responsive table, list or tree,) or a relevant control for your use case (for example a chart or the category navigation pattern) may suffice.

Types

Fully Responsive Tables

Responsive Table (sap.m.Table)

Based on the list, the responsive table provides:

• An optimized view of a line item at a glance without any horizontal scrolling, regardless of the screen width.
• Full flexibility for table content:
  • Any SAPUI5 control can be used in a cell, including micro charts and forms.
  • Using layout containers, such as a grid layout, allows more than one control to be used in a cell. Consequently, the cell shows more than one data point.
  • Templates with multiple rows are supported, so different items can have different layouts. For example, this can be used to show editable items and read-only items in the same table without switching modes. In this case, the editable items could have a completely different layout than the read-only items.
  • Items with different heights are supported. This allows for more dynamic content in cells, for example, to show lists or use text controls that wrap instead of truncate.
• Smooth scrolling. This is done by rendering all items on the application background. Thus, the responsive table does not have its own scrollbar but uses the scrollbar for the whole page.
• A very lightweight design.
• Touch interaction support.

List (sap.m.List)

Tree (sap.m.Tree)

Desktop-Centric Tables

The following tables belong to the desktop-centric table group:

• Grid table: This is the most basic table in this group.
• Analytical table: This provides the following features on top of the grid table:
  • Grouping by several levels.
  • Automatic calculation of grand totals for a column and subtotals per group level.
• Tree table: This provides a hierarchical view of the items.

Grid Table (sap.ui.table.Table)

The grid table provides:

• An optimized way to show large amounts of data. It supports an unlimited number of rows. It also supports a very condensed display of line items on non-touch devices, thus allowing more rows to be displayed on the same screen property.
• Fixed control height, thus supporting horizontal and vertical scrolling (“viewport scrolling”). However, this also means that there are several vertical scrollbars on the screen for the page and table, which might be cumbersome on smaller screens.
• Touch interaction supported.

Analytical Table (sap.ui.table.AnalyticalTable)

The analytical table is based on the grid table and is therefore quite similar to it.

In addition to the grid table, the analytical table provides:

• Multilevel grouping
• Display of grand totals per column and subtotals per group

Tree (sap.m.Tree)

The tree table is based on the grid table and is therefore quite similar to it.

In addition to the grid table, the tree table provides:

• One hierarchical column

Resources