major
minor
There is currently no way to customize the ConfigKey of a TableComponent, which is generated in the private method "createTableData()" based on the component name.
If you now use different views with the same "layout.xml" (in which the TableComponent is used), this means that, for example, the column sorting is not retained when you switch back and forth between the different views. This is because the sorting is saved under the `ConfigKey` in the personal configuration and is therefore always overwritten by every other view, as they all use the same ConfigKey.
It should therefore be possible to customize the ConfigKey according to your own wishes, for example by adding the displayed model type of the respective view as a suffix.
The same applies to the TreeTableComponent.
Implementation
A configuration option has been added for the tables "User-defined configuration key" with which a model-dependent ConfigKey can be created from the model and the component name.
Test
- Switch to Technical demo > Components > Tables and trees > Table
- Edit component and configure x -> $x[1].inRevision($x[0]).get(`DemoTypes:A#name`) as "User-defined configuration key".
- Expectation: Different columns can be selected for different A's.