Who would benefit? |
Using table view with entities that have a large number of attributes |
What impact would it make? |
Shorter load times. Efficient evaluation when working with a large number of records |
How should it work? |
On high level, leveraging the multi-select CVL concept to include only fields of interest. Similar to how it works in Content Store. |
Why is it needed? |
Card view works fine with smaller data sets. Table view is better for large data sets but the way it works today is like 'All or Nothing'. It would probably increase adoption of Table View. |
Additional feedback, background or context:
We are currently working on enhancing our table view to an inline-editing view, including the possibility to dynamically adjust what columns to show and hide.
Please stay tuned for further updates via our marketing channels and release notes.