Since a few months now, one can only add up to 7 grouping properties to the standard pivot widget in workshop. It is possible to extend this by creating a function-based pivot table. However, the filter functionality is not providing the same functionality.
The issue arises from the fact that the standard pivot widget correctly applies the boolean filter logic to the selected groups while the function-based pivot widget only shows the sets of selected groups and leaves out which combinations were selected. Therefore, when trying to use this struct variable for filtering, you will not be able to achieve the same results but only filter down to all possible permutations. Under certain circumstances, this can lead to dataloss e.g. when a function-based pivot widget is used to filter an object set for a delete transaction.
Would it be possible to remove the ceiling for grouping properties in the standard pivot widget? Since the ontology only allows strict schema, every usecase where we have objects depending on a year number with a lot of additional information is impacted since users usually want to see all the metadata properties of a series as a column value and then the actual value in a year column.
For this usecase, the pivot widget itself is not doing an actual aggregation since it is actually partially transposing the table to a wide format and then showing the relevant metadata properties. I could imagine that this usecase of displaying the generally long displayed data in a userfriendly wide format with multi-level grouping similar to pivot tables could be a reason for its own widget.