Table view data type

Who would benefit?

Many customers, especially within fashion industry or manufacturer, who need to collect array data.

What impact would it make?

Having a table support out of the box would make the enrichment simplified, and at the same time natural way for the users to edit array data.

How should it work?

As a field type setting, a setting is used to define the behavior for each column in the table (JSON format). For each column, the following parameters should be possible to edit:
- id
- label (localized)
- data type (string, number, double, boolean, datetime, cvl)
- CVL id (if applicable)
- MandatoryFlag
- RegExp

In Enrich, when a string field is configured as a table, there must be an icon for table. When the user clicks on the icon, a table is displayed based on the configuration, where data can be edited in the grid, and a row can be added or removed.
For each column, the data entered must follow the configured data type, so that the data is entered as expected. Mandatory fields are not allowed to be left out, and if data is not passing through any RegExp the field must be turned into an error state.
The data is stored in the field as JSON format, and the table editor is intended for Enrich editing only (not expected for mass update or Excel imports).

Why is it needed?

To prevent bad architecture, or clumpsy solutions that is difficult to use or causes unnecessary events and performance issues.