Hi
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.
Shame - unless I am missing something?
Andrew
1 Like
Try a Query column, with whatever filters you need, make it a single query, sort by date descending, then a lookup through that query.
1 Like
You are a wonderful person Darren - thanks loads
2 Likes
Thanks again Darren
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.
Oh well
Thanks again though!
Andrew
1 Like
