[thread] New Table Feature Announcements

[w2go]

Is editable fields in tables that are grouped coming? Or is for some reason not possible?
Currently edits are disabled when the table is grouped.

[w2go]

For the groups, a custom sort option would be amazing. Or at least sorted by the way it appears in the data (which we can then manipulate) -- no sort.

[andoliveyou]

You can now configure dynamic columns from the advanced settings popover. Enabling dynamic columns will create columns for every key in your data source that does not already have a static column defined. Additional format options can also be configured per column format (i.e., number, currency, etc.)

[AnsonHwang]

Hello @andoliveyou , where to find the doc for this dynamic columns? thanks.

[jclutterbuck]

Excited to have this but, like @AnsonHwang, I don't understand how to use it? I found the option and then there is Label, Format, Hidden, Column Properties (which seems to be same as Format?). Doesn't seem to be anything I'm familiar with from the legacy table.

No Tooltips or docs?

Thanks

[andoliveyou]

@AnsonHwang and @jclutterbuck, thanks for the feedback! We've gone ahead and added some in-app docs which will be available in this week's release.

[yoav]

Any updates here?

[andoliveyou]

Hi everyone! Following up here again to announce some additional table features. We've added:

1. Aggregation cells can now be rendered in grouped rows! While editing a column, you can select your desired column using the Aggregation option.

2. You can also enable a summary row in via Table add ons and configure default options for each column by clicking the add on editor. End users will be able to toggle desired aggregations from the summary row component itself.

[bradlymathews]

Fantastic! I have two clients that will really like this.

I am playing around with how to implement this for one of them.

When you have more than one group level, it would be super nice to show the count of how many unique items are in the lower level.

I have an imperfect hack. The grouping is on Type and Town text fields. Each Type and Town also has a id and I use unique count on the town id column and call it Town Count. The issue is the Town Count column always shows 1 when it is visible. Makes sense as there is on one of each town. The individual record shows the actual id value. Confusing. Is there a better way?

[andoliveyou]

Ah, that's interesting! I don't have a better solution for you at this time.

I can think of a couple paths forwards:

• We could make the aggregation right of the grouped column's configurable
• We could introduce a special column setting that enables users to hide non-aggregation data

I'll bring this feedback to the team.

[Tess]

We added the json column type to the new table

[AnsonHwang]

It sound so great. I try it just now, but can't type any character into it, event start with {, what happen?

[Tess]

I see what you mean I'll check in with our team about this

[jg80]

Not sure if this has been split off into another topic, but there are some oddities and some feature requests in the aggregation functionality that would be nice to resolve:

1. Issue: When aggregating by Average, NULL values are interpreted as 0. While possibly valid if a user intends NULL to be interpreted as 0, but usually NULL is meant to be NULL and calculation of average should ignore these records.
   In other words, average(2, 3, 0, 7) = 12 / 4 = 3 while average(2, 3, NULL and 7) = 12 / 3 = 4.
   Perhaps a switch to allow both options, but if not, defaulting to NULL being not counted as an observation instead of NULL = 0 is more appropriate.

2. It would be useful to add FIRST_VALUE and LAST_VALUE to the default aggregations. This is especially useful for time series (i.e. when grouped, show the final result of a running total column). MIN/MAX doesn't always work here as a field could be declining or increasing over time and therefore the final value might be either the MIN or MAX (or, frankly, none of the above).

3. I don't have a specific use case for it, but having the ability to aggregate by MODE may also be useful

4. I'd really like to enable/disable aggregations by level of grouping. For example, it may make sense to sum a field for the lowest level of grouping, but not across the top level of grouping. If I could hide the aggregation at the top level and leave it on for the lower level when expanded, that would be great.

Thanks!

[jclutterbuck]

I would also vote for FIRST_VALUE and LAST_VALUE.

I would also like to have a concatenation (CONCAT) summation (tricky I'm sure). But I'm often wanting to summarise text fields, and first/last is okay but sometimes, if it's just a few characters, or just a few entries, it would be nice to have them concatenated?

[Tess]

We've added the 'add row' functionality to the new table component (more info here)