Mass editing allows users to change multiple (homogenous) objects simultaneously. Usually, these objects are selected from a list or table and have most or all of their changeable facets in common, such as Object Name, Object ID, or Description.

By aggregating all the values of each of these facets, users can quickly choose to either keep or overwrite them.

Usage

Use mass editing if:

• Users need to change one or more values for multiple objects.
• The list that the objects are selected from is homogenous; that is, the objects have certain editable aspects in common.
• The values that need to be changed are common to all objects.

Do not use mass editing if:

• The list that the objects are selected from is heterogeneous; that is, the objects do not have any editable aspects in common.
• The objects that need to be edited have no (or barely any) common aspects.

Components

The two main controls used during mass editing are the combo box and the select control. Mass editing is usually done in a dialog. However, in a split-screen layout, multiple items can be selected in the master list and edited directly in the details section without the need for a dialog.

Both the combo box and the select control are used to aggregate multiple values of the objects to be edited. While the combo box allows the user to enter values that differ from the existing values, the select control limits the user’s choice to a predefined set of values.

When you build an app with SAP Fiori Elements, mass editing is achieved using smart multi input and smart multi edit controls. SAP Fiori elements deviates from the standard design but still works similarly. For more Information, see Mass Editing with SAP Fiori Elements.

Behavior and Interaction (incl. Gestures)

Mass editing can generally be applied to any type of object facet that can be edited.

1. The table above (first image in the carousel) contains 10 employees. While they all share the same columns, the values for each entry are usually different. There are of course exceptions, for example, if employees have the same name.
2. The second image shows how all the columns can be represented as combo boxes or select controls. If the values of a certain column are different, the user selects < Keep Existing Values >. If all the values are identical, the respective value is shown directly (see Website or Salary).
3. Image three shows a combo box that allows the user to type in a new website for all employees, leave the field blank, or keep the previous values. In this case, the latter is identical to selecting sap.com. This entry allows users to undo any changes they may have made. It is especially helpful if many preset entries are available and the user is unsure of what the original value was.
4. The last image shows a select control that restricts the user’s choices to the presets shown – no free text input is possible. Because of the employees’ different ratings, <Keep Existing Values> is preselected.

From Regular Editing to Mass Editing

The transition from regular editing to mass editing is very simple. The existing values are listed in a combo box or select control depending on whether the user is allowed to add a custom entry or if the choice is restricted to a predefined set of entries.

If the values of the selected objects differ from one another, the entry < Keep Existing Values > is preselected.

If all the values are identical, that specific value is used as the preset value. Exception: If the original entries were put into input controls that have all been left empty, the entry < Leave Blank > is preselected.

< Leave Blank > must only be offered if the input fields on the original objects are allowed to be left empty.

In the screen below, you can see the table from the first example. To edit a name, a user would usually select (or navigate to) one employee and click Edit. In edit mode, the employee’s name is represented as two input fields for the first and last names.

If, for example, the user wants to edit all the last names at once (mass editing), all the last names are aggregated into one single combo box (in the top right-hand corner). Because of the many different values, the preselected entry is < Keep Existing Values >.

In the dropdown list, all the values (last names) are listed in alphabetical order and without duplicates. Selecting one of these names would overwrite all the last names with that entry.

If permitted (by the design and the back end), the user can select < Leave Blank > to put a blank value into this field for all the employees.

In this example, a combo box was used, so the user can also type in a new value that is not represented in the dropdown list. All the existing last names are then overwritten with that new value.

If the user is not allowed to enter a custom value, you must use a select control instead of a combo box. All the permitted values must be listed in the dropdown list.

The following list shows how to “translate” controls into their mass editing equivalent. Each control is represented in two sections:

Checkbox

Composite Fields

Date Picker

Input (any characters allowed)

Input (restricted to specific characters, such as numbers)

Input (with value help or select dialog)

Radio Buttons

Rating Indicator

Segmented Button

Slider

Switch

Toggle Buttons

Guidelines

• Ensure that < Keep Existing Values > is always the first entry.
• If applicable, < Leave Blank > should always be second.
• Display all other entries after the two entries mentioned above. These additional entries can be all the values from the respective facet of the selected objects and/or all permitted values.
  Ensure that you list all necessary options/presets that the user can choose from.
• Usually, mass editing should be done in a dialog after selecting multiple items from a list or table and clicking Edit.
  There is one exception: In a split-screen layout multiple items can be selected in the master list and edited directly in the details area, without the need for a dialog.
• If your application also allows the creation of objects that the user can edit via mass editing, try to structure both create and edit screens similarly. This reduces the cognitive load for the end users. The same rule applies if your users have an additional SAP Fiori application for creating the object.
• If certain fields belong together semantically (such as First Name/Last Name or City/ZIP Code, arrange them in such a way that the user can recognize the connection.
• If a dialog is used to pick a new value (for example, value help), and the user clicks Cancel in that dialog, the previously selected value (or choice) must be restored to the field the dialog was triggered from.
• To decide when to use which dialog (value help or select dialog), see the usage guidelines for the respective controls (direct links: Value Help, Select Dialog).

Exceptions

< Leave Blank >

Only offer the < Leave Blank > option in the dropdown list if the user is explicitly allowed to leave a field empty and the back end supports it.

If the fields of a specific type of all selected objects are empty (such as Name), it is better to preselect < Leave Blank > instead of showing an empty combo box or select control, and having a blank entry in the dropdown list.  Even though this is not consistent, it provides a better user experience.

Special Characters (“<” and “>”)

The entries < Keep Existing Values > and < Leave Blank > should always be used as described in this guideline: They must start with “<” followed by a blank space, and end with a blank space followed by “>”.

These two characters have been chosen because they are not usually used in text form in objects.

In the unlikely event that these characters are already used by a customer, replace them with another set of unlikely special characters that are not used by this customer. However, you must still ensure that < Keep Existing Values > and < Leave Blank > stay at the top as the first two entries.

Mass Editing with SAP Fiori Elements

SAP Fiori elements behave differently to the designs described above. When users choose to select a new value, an extra field appears underneath the dropdown (rather than a dialog). This new field reflects the type of input required in the respective case, for example an input field for text or numeric values, or a date picker for dates.

Resources