Workaround for filtering by some computed columns in glide big tables

Hello!

I have been employing a technique to work around some of the filtering limitations of glide big tables which I have not seen mentioned around here.

For example, I have a table of bookings which are related to different schools, so each booking is for a particular school. Now if I want to filter those bookings by school type which is a non-computed column in the schools table I can’t do it through a lookup column at the moment with big tables.

What I have been doing is creating two queries.

  1. One query is for the schools table where I filter that column by the school type and then I created a joined list of all the rowIDs from that query.

  2. Then I make another query for the bookings table and in that query I specify if the schoolID column is included in the joined list of rowIDs from the school query.

this can also be fully dynamic with a custom filtering system where I create user specific columns that the user inputs the school type and it queries the school table which in turn queries the bookings table for those specific schools.

I hope this makes sense and is something useful for everyone! I can always make a video if it need be for more clarity

3 Likes

Yes. I’ve been using variations of the same approach. Works well :+1:

2 Likes