The SAP Fiori elements list report template supports the three content area layouts detailed below.

For design information, see General Layout and the links below.

Simple Content Layout

The default layout for the content area is the simple content layout and displays the data for one business object in a single table view.  It supports:

• Display of one business object in one table, or — with SAP Fiori elements for OData V2 — in one list
• Display of data as a chart visualization
• Automatic data loading
• One table toolbar
• Creation of business objects via a dialog

Multiple View Layout

For more complex scenarios, you can turn on the multiple view layout which supports: 

• Display of one business object in a table with multiple views, for example, each view of the same table can display different columns or pre-filtered states
• Display of data as a chart visualization
• The segmented button for a maximum of three views or the select control for four or more views
• Display of the count or number of total rows in the view (must be enabled)
• One table toolbar
• Automatic data loading

Note that Developers refer to this layout as ‘single table for all views’ or ‘single table mode’.

Multiple Content Layout

To support even more complex scenarios, you can turn on the multiple content layout which supports: 

• Display of multiple business objects in multiple tables, for example, you can display a customer overview with different tables for invoices, deliveries, and overdue payments. All the tables can all be filtered by a specific customer and a specific date.
• Text-only icon tab bar to switch between business objects
• Display of data as chart visualizations
• Automatic data loading
• Different toolbars for each business object

Note that developers refer to this layout as one of the following:

• One business object as a separate table for each view or multiple table mode
• More than one business object as multiple views in a list report with different entity sets and table settings

Related Links

Want to dive deeper? Better understand the related desgin guidelines? Or, refer the development team to the related documentation for implementation? Follow the links below.