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.
QuickBaseCoachD
7 years agoQrew Captain
Right, hence the suggestion to only Sync across EEs who did have a userid. There is a filter when you build the Sync Connected table.
As for building the Connection, if the employee data is in a different app, you will need to make a new Quick Base Connection to get at that other App. Note that these Connections are owned by a user, so its best practice to have them owned by a userid which is like an Admin userid that is not actually a person, but rather a userid owned by the IT department.
As for building the Connection, if the employee data is in a different app, you will need to make a new Quick Base Connection to get at that other App. Note that these Connections are owned by a user, so its best practice to have them owned by a userid which is like an Admin userid that is not actually a person, but rather a userid owned by the IT department.