This is the default table in SAP Fiori. If a table is needed, the responsive table should be the first choice. It is based on the list.

The responsive table provides:

• An optimized way to show a line item at a glance without the need for horizontal scrolling, regardless of the screen width.
• Full flexibility in regards to 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 of the whole page.
• A very lightweight design.
• Touch support.

The responsive table is limited in the following way:

• Since all items are rendered, the responsive table is limited to approximately 1,000 items on one screen (depending on the complexity of the items and the whole screen). Exceeding this number can lead to decreased rendering performance. On mobile devices, browsers can also run out of memory.

The list is the basis for the responsive table. It should be used whenever a table is too complex.

The list provides:

• Full flexibility in regards to its content:
  • There are various specializations for specific list types.
  • With a custom list item, all SAPUI5 controls can be used inside a list. Using layout containers allows more than one control to be used in a custom list item.
  • Templates with multiple rows are supported, so different items can be shown in the same list.
  • Items with different heights are supported.
• Smooth scrolling. This is done by rendering all items on the application background. Thus, the list doesn’t have its own scrollbar but uses the scrollbar of the entire page.
• A very lean and lightweight design.
• Touch support.

The list is limited in the following way:

• Since all items are rendered, the list is limited to approximately 1,000 items on one screen (depending on the complexity of the items and the entire screen). Exceeding this number can lead to decreased rendering performance. On mobile devices, browsers can also run out of memory.

The tree is based on the list. It should be used whenever a hierarchical view is needed, but a tree table is too complex.

The tree provides:

• A standard tree item that provides an icon, a text (that wraps), and a counter.
• Support for items with different heights.
• Smooth scrolling. This is done by rendering all items on the application background. Thus, the tree doesn’t have its own scrollbar, but uses the scrollbar of the entire page.
• A very lean and lightweight design.
• Touch support.

The tree is limited in the following way:

• Since all items are rendered, the tree is limited to approximately 200 items on one screen (depending on the complexity of the items and the whole screen). Exceeding this number can lead to decreased rendering performance. On mobile devices, browsers can also run out of memory.

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 devices are supported.

The grid table is limited in the following ways:

• Content layout is less flexible:
  • The grid table supports only certain controls, mainly for displaying text or getting single-line text input from users. For example, you cannot add micro charts.
  • Only one control can be added per cell.
  • It supports only single-row templates.
  • All items need to have the same height.
• Vertical scrolling is not smooth. For performance reasons, the content is not really scrolled but exchanged.
• The design is more complex.
• Although touch is supported, the grid table works only on desktops and tablets. For smartphones, a fallback solution is needed.

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

The analytical table is limited in the same way as the grid table, with one addition:

• The analytical table needs analytical binding.

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

The tree table is limited in the same way as the grid table.