Universal Table Access Everywhere in Glide Apps

I would like to request a universal table that can be accessed everywhere in Glide Apps. This would be a big help to developers. Currently, there are limitations in accessing tables in apps, and some functions cannot be implemented due to these limitations. For example, to set the visibility of a screen, you must use the User Profile table and no other option. There are many times when we need to set certain settings and have access to them globally.

It would be very useful to have one single row table as a global resource table that is visible everywhere in the app just like the current User Profile table. This table could be called “App Global Settings” and could have columns for Template columns, JavaScript functions, Header and Footer text, and many more. We could access the table fields from anywhere in the app design, including screens and tables design. In the app design, we could simply select the column from the drop-down. In the table design, we could reference the table columns simply by using something like AGS.ColumnName or #AGS.ColumnName. This would be like AGS.PhoneNumber Formated Template, AGS.Header, and AGS.Footer or #AGS.PhoneNumber Formated Template, #AGS.Header, and #AGS.Footer. All this without having to create a relation column. This way, we would only include the column we want, thereby minimizing the risk of exposing sensitive data in case Row Owner or User Specific Column is not being used.

Allowing Glide developers to create the “App Global Settings” table and assign it as a settings table would be a great feature. This way, Glide Apps would know to treat it as a Settings Table.

At the very least, allowing us to create a table that is globally accessible just like the User Profile table would be invaluable.

Thank you for considering this.

lessening the silo effect is a good thing. Universal table!! fantastic idea. simplifies glide datatables relations etc… brilliance Monj

1 Like

Agree. I was surprised that this was not an option. Of course the work around is link to users table with a Single Value Column… and then use different lookups to expose the data you need.

Would be nice to not have to do this :slight_smile:

1 Like

@AdamMartin, yes, the workaround is too much and does not work in some situations. Thanks for upvoting it.

1 Like