New Table features

Announcements
1

Hi all,

We’ve recently released a number of power-user enhancements for the Table component:

Custom Sort Modes

Custom sort modes allow overriding the default sort ordering for a column - you can sort by raw data values, or define an ordered list of options for sorting. See our documentation here.
sort modes2

Auto-column-width mode

Auto-column-width mode sets column widths automatically based on the content width and the table width, maximizing the amount of visible data while removing unsightly horizontal scroll bars. This can be enabled in the inspector under Appearance -> Advanced.
auto column width 11

Multi-column sorting

Multi-column sorting is available via shift-clicking on column headers, and as a default configuration in the inspector under Interaction -> Advanced.
multi-sort

These features are available now for all Cloud orgs, and will be made available for on-prem users soon - feel free to take them for a spin, and let us know if you have any questions or feedback. Happy building!

14 Likes
2

Custom Sort Modes seems to be broken, or at least the 'raw' mode.

My use case (that is super common) is that I have a column corresponding to days to an SLA. I set the Mapped value of the column, of course to format the SLA as {{ ${-item} d ago }}

So from my understanding Sort mode > Default would sort by the mapped value of the column (by the default of that type; strings lexicograpgically etc)
And that Sort mode > Raw would sort by the actual column value taken from the source, ie {{ item }} before being transformed by the mapped value. However this behaviour does not work at all, the sort order appears to be exactly the same as Sort mode > Default

For a reproducible example: just use any numerical column, set the mapped value to {{ ${-item} d ago }}, then set Sort mode > Raw