What is the proposed idea/solution?
It would be a game changer when working with hierarchical data for the roll-up field's ARRAYUNIQUE(values) function to return clickable linked record values instead of a comma-separated string when aggregating a linked record field from the source table.
Currently, users can only represent one level of a linked record hierarchy as linked record values using lookup fields without risking duplicate linked record values. Multi-selected linked record lookups/roll-ups can lead to confusing UX and fewer group-by options.
How does is solve the user problems?
This would serve as a workaround for the strange user experience that occurs when using a roll-up field to return a lookup field of multi-selected linked records. This can duplicate of the same record referenced in the roll-up/look-up field.
How was this validated?
For example:
Let's say you have a base with three tables containing linked records in this hierarchy:
Dashboards -> Data Sources -> Tables
and you want to see a list of Dashboards related to each Table.
In Tables, you would normally create a lookup field to a linked record field in Data Sources that is linked to Dashboards. The duplicated values problem occurs when a single table record is linked to multiple data source records, which are also linked to multiple dashboard records. This results in duplicated dashboard records appearing in your lookup field (which creates confusing UX in general, but also makes grouping by this field even more problematic than usual for multi-selects).
Who is the target audience?
Intermediate base builders, everyone.
