Table to be available in visibility and filtering options

To have another table , like a table with the main settings for an app/page, that can be displayed in every visibility and filtering condition, like the user profile table is.

I’ve thought about this too several times, but I could never quite justify it in most cases. First of all, when you use values from the user profile table, it knows exactly which row in the user table to pull those values from. If glide allowed you to specify any other table, which row would it use? Would it always default to the first row? Would you specify which row to look at?

If a user is signed in and you use user profiles, it just made sense to me to use single value columns in the user table to retrieve values from another table and make them available for visibility and filtering. If the app doesn’t require a user to sign in, then I can still create a single relation and lookup columns in other tables where I need to use those values for visibility and filtering.

I think the biggest advantage to having a separate non-user table as a global table is that you wouldn’t have to rely on a user being signed in to have access to global values. I’ve mulled over the idea, but haven’t quite convinced myself that it’s needed yet.

How I see it, is like a table with just one row and a column for each setting that is needed.
It could work also like you said … select the row first and then the data for multiple rows and by default it looks on the first one.

I have an app using 20 tables … in 20 tables I need to pull in that data, that is static in order to be able to create the visibility and filtering condition of that table … not the best scenario … and in this case it doesn’t matter if the user is logged in or not.

Let’s say for some visibility or filtering condition I have a static value of 1 …then I need to add that static value by default in each user profile … it could work, but still, not the best experience and you will have a lot of data stuck in the user’s profile table that is not related to the user, because is related to the app.

Anyway … I hope this makes sense and also … thanks for the idea of putting the data in the user’s profile … until now I was adding the data manually :roll_eyes:

1 Like