User Fields Best Practice
I have users (of course) and then a 'Team Members' Table. The reason for that table is I have other info (phone numbers, employee IDs, etc) that I want associated with each user. I then have a tabl...
Forum Discussion
MarkShnier__You
Qrew Legend
Qrew LegendIt's an insightful quesiton.
I did a major app for a client and we went with the "six fields" based on their respective functions on that project. While a many to many Resource assignments table might sound more elegant, in fact, you then will need to float up who the Project Manager is and who the Scope Writer is anyways, so that is a lot of formuals.
Also note that you cannot control Role permissions access to parents based the Role access to child records. So for example may want to say limit access to view to only where the current user is a child team member on that project. That will not work due to how Quick Base calculates. It starts with the parent and then decides there is no access, therefore it cannot calculate any thing about the children for summary fields, so no access to Parents.
So just KISS and slot in 6 fields for 6 user field titles on the Project.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
I did a major app for a client and we went with the "six fields" based on their respective functions on that project. While a many to many Resource assignments table might sound more elegant, in fact, you then will need to float up who the Project Manager is and who the Scope Writer is anyways, so that is a lot of formuals.
Also note that you cannot control Role permissions access to parents based the Role access to child records. So for example may want to say limit access to view to only where the current user is a child team member on that project. That will not work due to how Quick Base calculates. It starts with the parent and then decides there is no access, therefore it cannot calculate any thing about the children for summary fields, so no access to Parents.
So just KISS and slot in 6 fields for 6 user field titles on the Project.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
- What about the third option where I actually make 6 of the same relationship, so I actually have relationship drop downs instead of just user fields? The reason for this is then I can bring over lookup fields of phone numbers and other employee info.
Or is there another way to do this if I just use the user field option?
------------------------------
Mike Tamoush
------------------------------- MarkShnier__YouYes, definitely. Six relationships and then you can filter the drop downs for each field perhaps according to the title of the users. Is your employee table going to have the key field as the user ID? That always proves a very useful technique.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------- Well,
I'm thinking about making it their Employee ID number for the following reason (unless you have thoughts otherwise):
I have a second table of all employees. This table does not have a user field because not all of these employees are QB users. This is mostly used for importing labor hours from time cards. The key field on that table is the Employee ID. I thought maybe somehow in the future it could help to have all the same key field?
But perhaps not - I don't have a specific use case yet.....
------------------------------
Mike Tamoush
------------------------------
