Cannot use Single in Glide big table

Ask for Help
1

Hi there.

I tried to use Single value in Glide big table but it doesn’t work. And I tried to use Relation from that big table. And also, it doesn’t save. Please help.

2

There are limitations to Big Tables, which are documented below:

If you tell us more about your specific use case, we may be able to suggest a workaround.

3

And also, I have just found that. It cannot use Roll up over than 100 rows. And why it named as Big table???

4

In Glide AI described how to solve this problem by using multiple relation. But it still doesn’t work out.

5

It depends what you are trying to rollup. If you are rolling up a non-computed column, there is no limit. If your are rolling up a computed column, yes the limit is 100 rows.

6

I tried this instruction step-by-step. But when I clicked save. It doesn’t allow to save.

“To create a Multiple Relation:

  1. In the Data Editor, add a new column

  2. Select Relation as the column type

  3. Specify matching values between tables (values must match exactly)

  4. Enable Match multiple option

  5. Click Done

Then use Single Value → First:

After creating the Multiple Relation, you can add a Single Value column that targets your Multiple Relation and select “First” to get a single value from the related data.

This approach lets you access Big Table data through the relation, then extract the specific value you need with Single Value → First.”

7

@Plai_Official , if you wanna extract a single entire row form a relation that is pulling data from another Glide Big Table.. then try these steps:

  1. Create a relation from the current row to the Glide Big Table
  2. Turn on “match multiple” for that relation column
  3. Build a new query column and set the source to that relation column
  4. Add a filter or use the sort option to sort the the field that will allow you to get your desired row at the top or bottom
    1. In my case, if i always wanna extract the latest row, i sort the query by my “created on” timestamp by “Z-A” so the latest timestamp comes first
  5. In your query, turn of “match multiple” to avoid returning more than 1 row

Hope this helps :slight_smile:

  1. Screenshot 2025-09-10 at 12.00.28 PM
    Screenshot 2025-09-10 at 12.00.28 PM1476×1606 96.1 KB
8

Because in practice, it can hold much more rows than a normal table. But as Darren said, there are limitations on the calculation side so that your device doesn’t have to do an enormous load of work when you use the app.