Hi,
I’m trying to create a global search bar that searches across multiple glide tables. I tried looking for something similar in the community and found this Creating a global search across all the tabs in spreadsheet - #8 by Jeff_Hager but I don’t see inline list as a component. Attaching a screenshot of what my search dashboard looks like.
Have a browse of the below thread:
Thank you @Darren_Murphy. That’s pretty much what I wanted! I have one problem though - now that I have 2 collections in a table with 2 different sources, I should be able to set the visibility condition based on columns from the corresponding table, right? For one of the tables, I’m seeing columns from a different table (the one of the main Navigation tab source). Attaching screenshot.
Overview - is the main navigation tab with Athlete Mastersheet as source
Overview > Table - is the table populated from Competition Entry source
If you see the visibility options, the options are coming from the Overview source, not the table source. This seems like a bug to me. Any way to work around it?
Why would you need to set visibility conditions?
If any of the Collections return no results, they won’t be shown.
The column headers are still seen when there are no results. Also, I want to have a ‘No records found’ text show up when there are no results.
Okay.
How are you applying the filtering?
What you could do is create a rollup column for each table in your User Profile row, that counts matching records. Then use those to drive the visibility of each collection.
And then display your “No records found” message if they are all empty.
Ah, I was adding the rollup coulmn to the same table and trying to use that. Thought that’s more intuitive by design because the if-else column is there. But adding it to users table get things working. Thank you!
Curious - what’s your rule of thumb when you design such things? Adding to users table seems like a hack sometimes to overcome the shortcomings of Glide.
Not really. The Users table is convenient for these sorts of things, because values can be read/written from anywhere in the App.
There has been talk about having an option to get/set global variables, but until something like that materialises, the User Profile row is the next best thing.
