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
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
------------------------------
Or is there another way to do this if I just use the user field option?
------------------------------
Mike Tamoush
------------------------------
MarkShnier__You
Qrew Legend
Qrew LegendYes, 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
------------------------------
------------------------------
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
------------------------------- MarkShnier__You
Can be extremely useful and apps to have a relationship to an employee table where the key feel this user ID because the reference field on the truck outside can be a formula field called current user.
The formula will be User()
That allows you to look up any information from that table automatically based on who the current user is and you can control permissions and report filters that way.that allows you to look up any information from that table automatically based on who the current user is and you can control permissions and report filters that way.
Therefore I suggest that you have the user ID be the key field and you can look up any information you want from the full employee table by Making a relationship to the full employee table and of course that will bring down the employee number along with any other information you need from the master employee table
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------- So really, my team members table can just be a list users with their name and maybe their title in this team. The reason for this is just so I have a table where I can make my user name field the key field. With this, I can grab other info from my master employee table.
In essence, the ideal situation would just be to use user fields, but I can't relate user fields to my employee table, so this is the work around. Correct?
------------------------------
Mike Tamoush
------------------------------