Skip to main content

MultiEditTable

MultiEditTable – Editable Table for Multiple Datasets​

The MultiEditTable ViewTemplate is used to display one or more datasets in an editable table format. Each row represents a dataset, and each column corresponds to an EntityField. The fields to be shown are defined via the property columns, while those that are editable must be explicitly listed in editableColumns.

To customize the appearance and editing behavior of specific fields, the properties viewRendererMapping and editRendererMapping allow the assignment of Renderers. These control how fields are displayed in view and edit mode. Further details are described in the section "Renderers".

Behavior and Characteristics​

General Properties​

  • Paging is not supported in this ViewTemplate.
  • Fields with unsaved changes are highlighted with an orange frame to indicate pending updates.

Supported Content Types​

The table edit functionality currently supports EntityFields with the following contentType values:

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

Unsupported Content Types​

The following contentType values are not yet supported for editing within the table:

  • SIGNATURE
  • LONG_TEXT
  • HTML
  • IMAGE
  • FILE
note

Unsupported fields can still be part of the table (e.g., for display only) but cannot be edited.

Example Configuration​

A practical example of this ViewTemplate is "MultiEditTable" in the View ProductpriceFilter_view, located in the Context "Productprice".

MultiEditTable

Client Appearance and Usage​

To access this configuration in the ADITO client:

Navigate to:
Sales > Prices

Initially, the Context displays a default FilterView with a regular table. To activate the MultiEditTable, switch the view using the view selection button in the upper-right corner of the FilterView.

The resulting table displays datasets with the following behavior:

  • Products
    Selection is handled via a combo box. The corresponding EntityField is PRODUCT_ID, which has a Consumer assigned. No Renderer is needed for this behavior.

  • Prices
    Editing is performed via additional action buttons. The EntityField is PRICES, and editing is enabled through the ViewTemplate's editRendererMapping, which assigns a Renderer of type NUMBERFIELD.

  • Validity (From/To)
    Selection is enabled through a date picker because the corresponding EntityFields VALID_FROM and VALID_TO each have the contentType DATE. No additional Renderer is required.

  • Price List
    Displayed with a background color. This is controlled by the viewRendererMapping, which assigns a Renderer of type BADGE to the EntityField PRICELIST.

    The background color is dynamically determined using the code in the colorProcess property of the PRICELIST field.

    tip

    For testing, you can override the dynamic color by setting a fixed value in the color property and clearing the colorProcess value using the "Restore Default Value" option in the context menu.