Forum Discussion
QuickBaseCoachD
7 years agoQrew Captain
No problem
If the employee are all users, you can set the Key field of the EE table to be the userid and then make a relationship to the details table using a reference field on the right side of the relationship of the field I like to call [Current User] with a formula user formula of
User()
If not all employee have userid�s or for other reason you are unwilling to change the key field, then you can make a Sync table of selected fields from the EE table and set the Userid in text format ( it will sync across as text) to be the key field. Only bring across EEs with a userid.
Then make a reference field with theformula
ToText(User())
To make the relationship.
If the employee are all users, you can set the Key field of the EE table to be the userid and then make a relationship to the details table using a reference field on the right side of the relationship of the field I like to call [Current User] with a formula user formula of
User()
If not all employee have userid�s or for other reason you are unwilling to change the key field, then you can make a Sync table of selected fields from the EE table and set the Userid in text format ( it will sync across as text) to be the key field. Only bring across EEs with a userid.
Then make a reference field with theformula
ToText(User())
To make the relationship.
WendyShoef
7 years agoQrew Cadet
FYI, it's not that we are unwilling to change the key field, it's just that there are employees that are not users of QuickBase. And also, we need to be able to see the information of employees that are no longer with the company in our reporting.