Ability to create a master table within a solution
Steven Z
I would love the ability to create a master table that would be able to pull the records from other tables. For example, the solution is Scheduling and the tables are Appointments, Meetings, and Employee Shifts (each with their own required fields). I'd love the ability to have a 4th table which is essentially the "master table" that pulls together the records from all of them. In that case, we would be able to see all the scheduling-related records in one calendar so we don't need to switch between several different tables.
Ideally, when adding a record to that master table, you can choose which normal table it goes to which would change which fields need to be filled out.
Thank you for your consideration!
Jon Darbyshire
Great to hear your perspective, Steven Z! I have a few more questions for you:
- Could you provide more details on how you envision the interaction between the master table and the other tables? For instance, would changes in the master table reflect in the other tables?
- What specific fields would you like to see in the master table from each of the other tables?
- Would you like the master table to have any unique fields of its own, or should it only contain fields from the other tables?
Steven Z
Jon Darbyshire Hi John, thank you for the follow up, it's greatly appreciated. I'll do my best to answer those questions. :)
- So I imagine the master table as a puller and displayer of information from it's child tables but ideally it should still be a 2 way sync so you don't have to click back in to the "home" table to edit it. So if a records information is changed from the master table, it would still update in the "home" table of that record.
- Ideally you would be able to pull any field from each of the normal tables (or at least as many as possible). If not it's fine since you could always click on the record to receive all of it's information. In the event that not all info can be displayed, it would be ideal to at least be able to pull the name of the record, any date field (so it can be viewed all together in a calendar), and perhaps the status field.
- I can't think of a reason the master table would need to have fields of it's own so perhaps not.
Thanks again for your consideration! :)