Hello, Gliders, As I continue to learn more Glide features and expand my apps, it results in some behind the scenes clutter and I would like to now tidy up. I think I like the new Column Grouping to help with this. Here is a question for the group–How much data is kept in your “Users” table? Do you tend to keep everything in one place? Biographical profile info, subscription payment info, user/member active status? I have 3 main bits of info on users. Their literal login information–email, name, profile created date Role–certain users are allowed to edit records. These are NOT team members that are managing the app. Simply end-users that have adding/editing privileges that others do not. A Relation column connects the User’s email address to the rows in another data table they are able to edit. Paid subscription status that tracks purchases through Stripe to allow access to paid content. Would you keep all of this info in a single Users table as profile information? Or might you have a more basic User table that is related to an Event Managers table and a Subscription Payments table? Very interested in your experiences and feedback. Thanks, Mona

In this very recent thread I asked the same question since I have wondered about this. [image]Table relations & choice as filter Now that you brought this up, from a design perspective I read (thought I read/thought I understood) that you should not use the ‘user profile’ table except for ‘user’ info from a security perspective. But the user profile is the one table that is accessible in actions, visibility and filters so it has become a very wide row with lots of USC/xxx columns with many templates/filters plus relations and is the source for four of my five TABs and many ‘New Screens’, Is this a reasonable/usual best practice? I especially needed access to data within actions which have a very limited scope. TIA @Jeff_Hager replied with good insight. Hope this helps. [image] Table relations & choice as filter Ask for Help Hi there, I am struggling to use a choice as a filter with following structure. I have TOPICS SUBTOPICS CONTENTS The properties relate like this: A TOPIC HAS MANY SUBTOPICS A SUBTOPIC CAN BELONG TO MANY TOPICS A CONTENT CAN BELONG TO MANY TOPICS A CONTENT HAS MANY SUBTOPICS The target UX is like this Step 1 User chooses one TOPIC only Step 2 User is shown a list of CONTENTS & can filter the CONTENTS with the “choice” component according to the SUBTOPIC (the “chips” are SUBTOPICS). …

Son of a gun - here is Robert talking about why he uses ‘users’ for this app versus other sources. [image]tornado Use Multiple Choice Components to Filter an Inline List New version! Check out the original post for the updated video. New features include: Using Users Table as the source for the details screen Show/Hide Filters toggle Multiple choice selection filtering Displaying an alert if filtering yields no results

I often use the users table as the source for my screens when I want to store selections or temporary values that I need to access in other tables. Example 1: Temporarily storing a rowID from another table so I can reference it in a relation, if-then-else column, or in a form submission. Example 2: Storing choice component values that need to be referenced in another table for filtering purposes The only time this differs is when I DON’T need to reference these values in other sheets. In this case, I’ll create a new table that uses user specific values to build out the functionality I need (aka a “Work table”). Example: [image] 🗓️ Dynamically filter an inline list by TIMEFRAME (Parts 1 & 2)! Community Resources wave Hey fellow Gliders! In this video, learn how to dynamically filter a list of records by timeframes (day, week, month, etc.) using a Choice component, some Math columns and a Make Array column. Also features the concept of a “Work Table” to keep your data tables lean! popcorn Enjoy! Part 1 [Glide: Dynamically Filter your Data by TIMEFRAMES (Part 1)] Part 2 [Glide: Dynamically Filter your Data by DATE RANGE (Part 2)]

Boom @Robert_Petitto . Worked like a charm. Many many many thanks Robert :smiley:

App maintenance/Clutter clean-up

Ask for Help

MattLB July 8, 2022, 6:37pm 3

Son of a gun - here is Robert talking about why he uses ‘users’ for this app versus other sources.

Topic		Replies	Views
Table relations & choice as filter Ask for Help	12	1689	July 7, 2022
Table to be available in visibility and filtering options Feature Requests	2	277	August 31, 2022
Filtering by one table, showing joined data from another Ask for Help	9	658	February 26, 2023
Multiple User Types with Different Relation Fields Ask for Help	5	439	June 9, 2023
User table design approach Ask for Help	1	69	September 17, 2024

App maintenance/Clutter clean-up

Related topics