I think the below is not possible using GBT - is that correct?
A Glide table of venues
A Glide table of contacts. Multiple contacts can work at one venue
A Glide Big Table of statuses - relating back to the contacts
Every time a status is changed - a row is added to the GBT with timestamp and new status (so I have a record of when statuses changed)
When viewing a venue, I want to be able to lookup the latest status of each or any contact that is associated to that venue. So it goes
Venue > Contacts (multiple) > Statuses (multiple)
I made the Statuses table a GBT as there will be many row. Regretting it now as I can not, it seems, do a look up from my venue table, via a multiple relation to the contacts table, of a multiple relation on a GBT
I think my only way is to do away with the whole logging idea, and just do set column values into the contacts field for whenever a status changes and look those up.
I have had to resort to manually adding to basic columns in my contacts table though (as well as to the log in the Big Table). When a log entry is made, it also adds to a basic column on the venue table the exact same values (YUK)
I have a choice component on screen which writes to a User Specific column. A Query Column then filters based on the choice. * is added to every option in the back end so that when no choice is selected, all rows are returned.
But the query column does not give me the option to filter by a Lookup column (on the venue table) that looks up from the Big Table (via the contacts table)
I can’t query from the Venue table to the log table either, as I am using the contact ID to relate on. (I also looked up the Venue ID from the Contact ID - but that didn’t work either - the Query on the Venue table would not let me filter by the Venue ID on the log table.
I am still struggling with this, and can’t work out how I can use Big Tables for this pretty standard use case scenario.
To summarise - 3 tables
Screen helper table - just one row. Glide Table
Contacts - 1,000 rows approx - Glide Table
Log / join table - 4,000 + rows and would grow - Glide Big Table
I have several user specific columns on the screen table for filter choices - with queries to the contacts table so the user can filter and search the contacts.
But I want them to be able to filter against status too. The status is stored in the Join / Log table. Each time the status changes, a new row is added with the ContactID, timestamp and new status.
So I need to query and lookup the latest status for each contact from the contact table.
I have tried a single Query filtering against Contact ID, ordered by timestamp - but that can not be selected in my Query’s filter option back in the screen table.
So the query / lookup works in the contact table - but it is not accessible from anywhere else through a query / relation / lookup / joined list etc.
I have had to resort to adding a row to the log table AND a basic column for each contact which is far from ideal.
Am I missing something / doing something wrong? It works perfectly when using Glide Tables. I just wanted to leverage the API v2 so that I can add lots of rows to the log table quickly and cheaply.
For a little more context - in my app, contacts get updated in bulk - say 100 at a time. Adding 100 rows to a table with the latest status is much quicker than looping through 100 rows and updating the status for each row.
