The SAP Fiori elements templates support the features and settings for the table toolbar detailed below.

For design information, see the guidelines starting with Table Overview, and see the links below.

Feature Availability

Features in List Report and Object Page

The information below relates to table toolbar actions and settings in both the list report and object page floorplans.

Table Personalization Actions

By default, Sort, Group and Order actions are enabled.

These actions are icon buttons that open the Personalization dialog to the tab for the corresponding action.

For specific use cases, you can disable the icon buttons. When you do, the user must open the Personalization dialog to access the actions.

Table-level variant management is not a prerequisite for personalization.

For more information, see Table Personalization (Overview).

Show / Hide Details

The responsive table toolbar displays the Show Details action when at least one column is hidden from the screen because of limited onscreen space.

After the user clicks Show Details, the the table displays the hidden information in the  pop-in area, and the action changes to Hide Details.

The importance assigned to a column determines whether or not the table displays its values onscreen when screen space is limited:

• The values from high importance columns are always displayed onscreen — as columns or in the pop-in area, depending on the screen size.
• The values in columns with low importance are first to be hidden.

By default in responsive tables:

• Key fields have the importance set to high in list reports.
• Other columns have the importance set to none and are handled like columns assigned medium importance.

You can change the level of importance.

Application-Specific Actions

You can define these actions and the text displayed on the buttons.

If the action navigates to a different application, the action can be hidden according to the user’s authorization or the screen availability.

For more information, see:

• Action Placement
• Terminology for Common Actions

Mass Edit

You can enable this feature in a draft-enabled list report for the responsive and grid tables with SAP Fiori elements for OData V2.

Users cannot apply the mass edit to a draft record, including one open in edit mode in the flexible column layout.

By default, the Edit dialog contains all the currently visible fields.

The application development team can adapt the feature by:

• Changing the fields that display in the Edit dialog. This includes adding a custom field to the dialog.
• Excluding certain fields from the key user adaptation of the dialog
• Replacing the standard save action with a custom save flow, with an extension

Note that application developers sometimes call this feature multi edit, not mass edit.

For more information, see Mass Edit.

Actions Disabled Until the User Selects a Row

You can set actions in the table toolbar to display as disabled until the user selects one or more table rows for the action.

Note that the development team may call actions that require selection “context-dependent” actions and actions that are enabled without a selection “context-independent” actions.

For more information, see UI Element States.

Conditional Enablement of Navigation Buttons

With SAP Fiori elements for OData V4, you can enable buttons that navigate the user to another page or application based on the value of a specific field.

With SAP Fiori elements for OData V2, this feature requires extensions.

For example, you can enable the Generate Purchase Order button only for sales orders with the completed status.

Messages for Critical Actions

For actions that you set as critical, you can display one of the following after the user triggers the action:

• A message toast confirmation
• A confirmation message box to ensure the user wants to proceed with specific critical actions

Also, the backend can require a confirmation on some actions. In this case, the confirmation message is always shown in a message box.

Example

For more information, see:

• Message Handling
• UI Text Guidelines for SAP Fiori

Messages for Destructive Actions

By default, a message is displayed for confirmation of an action that will delete or destroy important data.

Example

For more information, see:

• Message Handling
• UI Text Guidelines for SAP Fiori

Multiple Views for a Table

You can display a table with multiple views, for example, each view of the same table can display different columns or prefiltered states.

For a maximum of three views, a segmented button is displayed. For four or more, the select control is displayed.

With SAP Fiori elements for V4, you can also display the row count for each view next to the view name.

List Report-Specific Features

The information below relates only to table toolbar actions and settings in the list report floorplan.

Standard Actions

By default, Create, Delete, and Export to Spreadsheet are enabled.

You can disable them.

You can also enable or disable the Delete button based on conditions specified in the backend.

Example

You can disable deletion for a sales order that has already been paid. When a user selects an item that cannot be deleted, the Delete button is disabled. In addition, if the user navigates from this item in the list report to the object page, the Delete button is hidden.

Create Object Actions

By default, the create via the object page feature is enabled. The create action opens the object page in create mode so the user can enter the data. Alternatively, you can enable object creation as described the sections below:

Via a Dialog

The action opens a dialog in modal view so the user can enter the data.

With SAP Fiori elements for OData V2, you can:

• Include a maximum of eight fields in the dialog
• Enable filter values saved in the filter bar to prefill fields in the dialog

With Default Values That Prefill Fields for the New Object

This feature is available with:

• SAP Fiori elements for OData V2 for applications without draft handling
• SAP Fiori elements for OData V4

Via a Dialog with a Reference to an Existing Object of the Same Type

With SAP Fiori elements for OData V4, application developers can build a custom create action via a dialog that lets the user create a new object with a reference to an existing object of the same type.

The user:

1. Clicks the action button.
   You can name the button to suit your use case.
2. Selects the value of the existing object to reference in the dialog.
3. Completes the fields for the new object by selecting one or more values to copy from the existing one.
4. Completes additional fields for the new object in the object page.

Hiding Actions in Multiple Content Layout

You can hide an action from a toolbar for a specific table when the list report contains multiple views with multiple tables.

For more information, see:

• Multiple Content Layout
• General Layout

Object Page-Specific Features

The information below relates only to table toolbar actions and settings in the object page floorplan.

Search

You can enable a search on the table.

For more information, see Search.

Edit

By default, Edit is displayed when the business object shown in the table is editable.

Delete

By default, Delete is displayed in edit mode when the business object shown in the table is deletable.

You can enable or disable the Delete action to allow users to delete only in certain conditions.

For example, after the sales items for a Sales Order have shipped, you can hide the Delete action for the items. When a user selects an item that cannot be deleted, the Delete action is disabled.

When multiple selection is enabled for the table, the Delete action is enabled if at least one selected item is deletable.

Subobject Creation

By default:

• Create is displayed in edit mode when the business object shown in the table is editable. For specific circumstances when the Create button is disabled, see Create Action Visibility below.
• The default creation action is via the suboject page — the action opens the subobject page in create mode so the user can enter the data.

You can:

• Enable or disable the Create action to allow users to create subobjects only in certain conditions. For example, after a sales order reaches the Delivery is Shipped status, you can hide the Create Sales Item action.
• Enable creation of a subobject via a dialog with 8 fields maximum. The action opens a dialog in modal view so the user can enter the data. The dialog must contain all the mandatory fields for the subobject. With SAP Fiori elements for OData V2, you can enable filter values saved in the filter bar to prefill fields in the Create dialog.
• Enable inline create for draft-enabled applications in grid and responsive tables with SAP Fiori elements for V4. See Inline Creation below.
• Enable default values to prefill the fields for the new object. This feature is available with SAP Fiori elements for OData V4, and with SAP Fiori elements for OData V2 for applications without draft handling.

For more information, see:

• Adding a Subitem
• Add Items

Create Action Visibility

Whether or not the Create action is visible in the table toolbar depends on:

• The object page mode.
• Whether the flow is global or local.
• Where the user enters the data for the new subobject — in the subobject page or directly in the table with the inline edit.

Inline Creation

With SAP Fiori elements for OData V4, in grid and responsive tables, you can enable inline creation of entries for applications with draft handling enabled. The Create action is displayed in edit mode.

The inline create action creates a new row where the users can enter the subobject data. By default, the new row is highlighted in blue and displayed at the top of the table. The highlighting disappears after the users save the data.

You can:

• Work with the development team to define a custom sort order.
• Enable default values to prefill the fields for the new object.

For more information, see Add Items.

Prefilling Fields for a New Object

You can turn this on in draft-enabled applications for the default create action via the object page, where the user navigates to another application to enter the data in the new object page.

The new object must be the main object on the object page.

You determine both the fields to prefill and the default values for the fields.

Copy and Paste from Microsoft Excel

By default, the table toolbar for responsive and grid tables displays Paste when the following are enabled:

• Draft-handling for the application.
• Inline creation for the object page table.

After users copy data from a spreadsheet, they can place the focus anywhere in the table except for the cells and trigger the browser paste with the keyboard shortcut (Ctrl+V for Microsoft Windows, Cmd+V for MacOS).

Limitations

• Pasting is supported only for fields that contain a single value, not for complex fields, such as smart links and images.
• If there are validation errors, a dialog displays an error message so the user can take remedial action.
• The greater the number of records copied, the longer the paste operation takes.
• The order of the of the data copied from the spreadsheet can differ from the order in the table in the application after the paste. SAP Fiori elements cannot control this.
• Users cannot paste data into custom columns of tables.
• This feature is not supported for custom tables.

Export to Spreadsheet

By default, Export to Spreadsheet is enabled with the copy and paste from spreadsheet feature above.

You can enable the button independently of the copy and paste from Microsoft Excel.

The Export to Spreadsheet button allows user to export the values in the table, including values in custom columns.

For more information see Export to Spreadsheet.

Full Screen Mode for Table Display

You can enable full screen mode for a table. However, it is generally not recommended.

Users click the Maximize action in the toolbar to display to the table in a dialog. They can return to the object page by clicking either the Minimize or Close action.

For more information on the restrictions for this feature, see Maximize/Minimize.

Content Switch for Table Views

By default, the number of views that you set for the table determines the UI control for the content switch for table views.

• A segmented button for a maximum of three views
• A select control for four or more views.

By default, the count or number of records in the view is not displayed next to the title of the content switch for table views for performance reasons. Talk to the development team about how displaying the counts impacts performance for your use case.

Related Links