MultiEditTable

Purpose

The MultiEditTable ViewTemplate displays multiple datasets in an editable table. Each row represents one dataset and each column corresponds to a configured EntityField.

Figure: MultiEditTable used for editing multiple records.

Behavior

The visible columns are defined by columns, while editable fields are configured separately through editableColumns.

Additional renderer mappings can be used to control the display and editing behavior of specific fields:

• viewRendererMapping for view mode
• editRendererMapping for edit mode

Unsaved changes are highlighted in the table. Paging is not supported.

Supported content types

Editing currently supports the following content types:

• UNKNOWN
• NONE
• TEXT
• NUMBER
• TELEPHONE
• EMAIL
• LINK
• PASSWORD
• DATE
• FILESIZE
• BOOLEAN
• FILTER_TREE

The following content types are not supported for editing:

• SIGNATURE
• LONG_TEXT
• HTML
• IMAGE
• FILE

note

Unsupported fields can still be displayed in the table but cannot be edited directly there.

Example usage

An example is the ViewTemplate MultiEditTable in ProductpriceFilter_view in Context Productprice.

In the ADITO client, it can be accessed under Sales > Prices. The view initially shows a regular table. After switching the ViewTemplate, users can edit price-related data directly in the table.

Typical behaviors in the example include:

• PRODUCT_ID as a selectable field through its Consumer configuration
• PRICES edited through an edit renderer such as NUMBERFIELD
• VALID_FROM and VALID_TO edited through date-based controls
• PRICELIST displayed with color styling through a badge renderer

Implementation hints

Paging is not supported in MultiEditTable.

Unsupported content types can still be included for display, but they cannot be edited directly in the table.