Forum Discussion
MattBlankenship
6 years agoQrew Trainee
Hey Mark,
Thanks for your reply.
I am VERY interested in the "Plan A" with automation.
I've got pretty decent Quickbase skills, and am definitely willing and eager to learn more. :)
In my "Time In/Out" table (child table), I'm guessing we will use the "User Name" field and the "HH:MM" duration field.
What fields do I need to make in the "Time Summary" table (parent table).
------------------------------
Matt Blankenship
------------------------------
Thanks for your reply.
I am VERY interested in the "Plan A" with automation.
I've got pretty decent Quickbase skills, and am definitely willing and eager to learn more. :)
In my "Time In/Out" table (child table), I'm guessing we will use the "User Name" field and the "HH:MM" duration field.
What fields do I need to make in the "Time Summary" table (parent table).
------------------------------
Matt Blankenship
------------------------------
MarkShnier__You
Qrew Legend
6 years agoOK, I will answer in pieces as I'm also dong real work.
We will need a new Parent Table called Employee Days.
Make a Relationship where 1 Employee has many Employee Days.
Can you tell me what is the Key field of the Employees table?
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
We will need a new Parent Table called Employee Days.
Make a Relationship where 1 Employee has many Employee Days.
Can you tell me what is the Key field of the Employees table?
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
- MattBlankenship6 years agoQrew TraineeI don't have an employee table currently. Since all employees have a Quickbase user ID, I just reference them as a user instead.
Do I need to make an Employee table?
------------------------------
Matt Blankenship
------------------------------- MarkShnier__You6 years ago
Qrew Legend
Yes, for this solution you will need an Employees table. You will set the Key field to be the User.
If you like you can then make a relationship to your Time Entries table based on your current user field as the reference field on the right side of the relationship. - the the choices will come down off a nice drop down that way.
On that Employees Table make a formula text field in the format of List("-", ToText(Userid]), ToText(Today()). Call it [Employee Day for Today]
so it will look like
jsmith@mycompany.com-04-01-20
Then make a saved table to table copy to copy all employees ot the New Table called Employee Days, where the Key field is a text field called [Employee-Day]
Lastly, make a relationship were One Employee Day has Many Time Entries and let it create a reference field.
Then edit that field called Related Time Day and rename it to be called Employee-Day and make the formula be
List("-", ToText(Userid]), ToText([Time Entry Date])
Then you will be able to make a summary field on the relationship on Employee Days to see the total duration.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------- MattBlankenship6 years agoQrew TraineeIt will not allow me to set the [Employee-Day] text field in the "Employee Days" table to a Key Field.
Also, just so I'm clear, I now have a text field named [Employee-Day] in the "Employee Days" Table, and
I also have a Formula-Text field named [Employee-Day] in the "Time In/Out" Table set as a reference field in the relationship of One "Employee Days" to Many "Time In/Out".
Correct?
------------------------------
Matt Blankenship
------------------------------