From the docs.
What does “100 matching rows” mean?
When querying a glide big table, and looking up a computed column, you are limited to the first 100 records. So, for example, if you are attempting to look up a computed column of an audit log, it will only return the first 100 records. There are some workarounds, but that’s the limitation.
I have two BTs: A and B.
I’m using row owners in table A.
I have a rollup column in table A that uses a relation to table B to roll up values in an if-then-else column.
Table B has 1,000+ rows, but for the row owners in table A, they will have < 100 rows.
I believe this works according to your logic (because of the row owners, I’m not rolling up all rows in table B).
Agree?
The 100 record limit is not impacted by row owners in table A. Rather, it’s how many rows you’re querying in table B.
If I have ID 1234 and I’m querying table B for all instances of ID 1234, I can only return 100 rows if the column I’m referencing in table B is a computed column.
My use case is…
Table B: 1,000 rows, a client has 10 rows
Some rows are red some are blue
I use if-then-else to get all the red and all the blue in diff columns
Table A: Rollup the values in Table B.red column, like so:
Because there is a relation, the result for each client is displayed in that client’s row in Table A.
My question was whether the 100 rows applies to each client or the entire table. If the latter, that can’t be right because the table has 2,000+ rows and the rollups all work correctly afaict.