Glide Big Tables - is it better than glide tables?

[ToOFa_Apps]

I see that the option to choose a glide table when choosing a data source is no longer there. But glide Big Tables is on offer. I assume glide tables are the default and big tables is where things are headed.
Can anyone give some clarity on the capabilities of big tables. Is it at least capable of doing what glide tables can do, can we use computed columns with big tables.
Any updates would be appreciated.

[MaximeBaker]

Here a thread that you read:

When to go in for Big Tables?

I have worked a lot with Big Tables right from the start, so I feel like I can share a few things that I’ve learned. My general rule of thumb is that I only use Big Tables for transactional type tables, where lots of rows are being added on a regular basis. If I expect the row count to climb above around 10k within a year, then I’ll definitely use a Big Table. When opting to use a Big Table, you need to think carefully about how it will be used, and how it will interact with other tables in yo…

Limitations of Big Tables

There are some features in Glide that aren’t compatible with a Big Table. These unavailable features are:

• Some Single Value columns that target Big Table columns.
• Multi Lookups into Big Tables (eg. Lookups via Multiple Relations or Lookups that target an entire Big Table column)
• Rollups are supported on Math, Template, and IfThenElse columns only, and only if those columns target basic columns.
• The Delete Rows action cannot be applied through a multi-relation in Big Tables.
• A Big Table cannot be the User Profile data source.
• Computed columns are limited to 100 rows.
• Computed columns cannot be used as filters in a Big Table.

[Darren_Murphy]

@MaximeBaker

There are some features in Glide that aren’t compatible with a Big Table. These unavailable features are:

• Some Single Value columns that target Big Table columns.
• Multi Lookups into Big Tables (eg. Lookups via Multiple Relations or Lookups that target an entire Big Table column)
• Rollups are supported on Math, Template, and IfThenElse columns only, and only if those columns target basic columns.
• The Delete Rows action cannot be applied through a multi-relation in Big Tables.
• A Big Table cannot be the User Profile data source.
• Computed columns are limited to 100 rows.
• Computed columns cannot be used as filters in a Big Table.

I realise that list is lifted directly from the docs, but the docs are somewhat out of date, and some of those points are quite misleading. Specifically:

@MaximeBaker

Some Single Value columns that target Big Table columns.

A Single Value column that directly targets a Big Table will not work. But a Single Value column that targets a Big Table via a Multiple Relation or Query will work. However, only Single Value->First is supported.

@MaximeBaker

Multi Lookups into Big Tables (eg. Lookups via Multiple Relations or Lookups that target an entire Big Table column)

Lookups via Multiple Relations and Queries are supported, but limited to the first 100 matching rows.

@MaximeBaker

Rollups are supported on Math, Template, and IfThenElse columns only, and only if those columns target basic columns.

Rollups (and Joined Lists) are actually supported for most computed column types, but limited to the first 100 matching rows. For example, a Joined List of a JavaScript column will work perfectly fine.

@MaximeBaker

Computed columns are limited to 100 rows.

This is misleading. It gives the impression that computed columns will only be calculated for the first 100 rows, which is of course incorrect. Where the 100 row limit comes into play is when you try to aggregate computed columns, eg. via Rollups or Joined Lists (see my comments above).

NB. All of the above assumes that the “More computed column support for Big Tables” preview feature is enabled.

[ToOFa_Apps]

Thanks for this, this helps a lot👍