My reflex in Glide is usually not to build static components like in a usual website builder, but to use collections instead. Not always nor everywhere of course, but generally.
In your case for instance, you have a table of Properties, presumably with a Type ‘Apartments/Villas’, and you could have a table of Types with at least two rows ‘Apartments’ and ‘Villas’. This would be akin to having things (properties) and categories (types). I would relate the tables, display the types in a collection and navigate to inline lists of properties on the detail screen of each type by clicking on the buttons.
That is how I would do it, but you can do it differently for sure.
Use a Custom Action that first sets a User Specific value somewhere, then navigates to the Property Page. Pull the User Specific value into the Property table as a Single Value, then use it as a filter on the Collection.
Thanks, I did not understand it in the beginning but got it working alright .
Thing is that this way it uses 1 Row and 2 Updates per Button Click which might not be a perfect solution.
Any other suggestions?
PS I just created for this a Table called Filter with a Row ID and a Column called Type, I take it that Glide understands that the Type Column is user-specific and applies it to a Public User or just a Visitor, right?
I’m not too sure I understand why you would use a helper table here. I know using helper tables for dynamic filtering with a choice component or navigation works well technically, but really it doesn’t work well, because it doesn’t scale well with pricing plans. Until pricing changes, if possible, I would avoid helper tables for dynamic filtering and navigation.
Here, I would use two tables, one for categories (types), one for things (properties), and a relation between the two, it doesn’t get much simpler than that. And maybe I’m missing something and if so my apologies
Add a helper table which contains all types of properties you have (Apartment, Villa, etc).
Add a query column to find properties to display (same type as this row’s type, status is active etc).
Build the home screen on top of your user profiles row.
Add single value columns that links to the correct row in the helper table. Say Single value > First > Helper table > Whole row to get Apartments, Single value > 1st from start > Helper table > Whole row to get Villas.
On your buttons, use Show detauls screen > Apartments Single Value etc to lead them to the right row and display the collection based on your query.