I have seen a few threads about this question. Just wondering if anyone has come up with a workaround.
Suppose I have a People sheet and a Teams sheet. And a person is joined to a team using a Memberships sheet (with a person_id column and a team_id column). How can I ensure that a person can only have one membership for a given team? Or, to say it another way, how can I ensure that every row in the memberships sheet is unique?
Or maybe there’s a way in the UI to show only Teams for which the current Person does not have a Membership? Like a “not” relation between People and Teams?
Yes. That’s what I’m currently doing. The form is creating a Membership row with a Person ID and a Team ID. But I can’t seem to find a way to show only Team choices for which the current Person does not have a Membership.
Yes. A person can join multiple teams, but should only be joined to a given team once. So, trying to prevent joining a given person to a given team multiple times.
Last question: is a person signing themselves up for a team? If so, this might be achievable…if an admin is assigning the person to the team, then this will be much trickier.
Question: can you describe some alternative ways of writing the “selected user” to the column in the Admin sheet? Asking because in my early experimentation with using Glide for a couple of apps, I’m encountering this pattern several times. Wondering about maybe additional/alternative UI pattens that would achieve the same end-result.
HAHA! That’s awesome. Ya…if I were to do this all over again, I’d probably want to separate my school account from my Glide account…bit late for that at the moment though…I’ll cross that bridge if it comes down to it.
If anything it gives people a “full picture” of my day-to-day lol