I am running an event where there are multiple participants that can participate in multiple events. I know how to link the Participants and Events tables together. However, I have a need for a view or third table that lists out each unique pairing of participant/event.
Example:
Person A: Event 1,2,3
Person B: Event 2
Person C: Event 1
Final Table
Person A - Event 1
Person A - Event 2
Person A - Event 3
Person B - Event 2
Person C - Event 1
This data will NOT be a one-time import. People will be added to the base regularly, events will be added as well. Signups will not be a one and done type thing.
A small wrinkle: Participants, Events, and Signups will all be added to this base via forms. Additionally, using automations and forms, event staff will need to be able to edit information in the records. I know how to set that up already. What I'm looking to avoid is a participant having to fill out multiple forms to sign up for more than one event.
What is the best base design for this? I know it's a unique ask and I'm happy to go into further detail if necessary.
Thanks!
Best design for multiple records linking to multiple other records, with unique final view.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.


