Best Practice for Linking Multiple User-Specific Rows Across Tabs in Glide

Hi everyone,

I’m working on a multi-tab Glide app that includes user-specific data like tasks, notes, and reminders. Each tab uses filtered data tied to the logged-in user.

I’m looking for a best practice or smart workaround to link user-specific rows across different tabs so that when a user updates something (like a task status), related data in another tab (like reminders) reflects the update automatically—without duplicating logic or breaking user privacy.

Here are a few specific things I’m curious about:

Can we maintain row consistency using Row IDs or relations across multiple user-specific tables?

Would using a helper sheet or custom action improve this process?

Are there any performance considerations or known sync delays when doing this?

Any help, sample apps, or ideas would be really appreciated :raising_hands:

Thanks in advance!
— jhonnmick

I assume this means data for each user, and not in the sense that you’re storing them in user-specific columns, right?

If you need it to happen that way, the related data must have a relation to the task status. From the relation, you can lookup the data from Tasks table so it always stay updated.

Yes, rowIDs is the right way to do it since it’s unique (and again, I’m assuming by user-specific, you mean you’re storing data that can be identified by a userID/email, not meaning you’re storing them in user-specific columns, or a table for each user).

I don’t think you need helper sheets for this.

If what you need is just lookups, then no.

1 Like