It looks to me that you have a theoretical relationship where one company has many assigned employees. You are trying to do it with a multi select field.
It looks to me that you have a theoretical relationship where one company has many assigned employees. You are trying to do it with a multi select field.
I think the fundamental problem is that a multi select field is really not designed for that purpose. And down the road it will cause problems for reporting.
And down the road it will cause problems for reporting.
My suggestion is to do with the traditional QuickBase way, which is to set up a relationship where one company has many assigned employees, and one employee has many assigned employees. In other words, you will set up a middle or joint table for the assigned employees.
You can still have a single field, which rolls up into the parent company record, which lists all the assigned employees, and conversely, on the employee's table you can have an embedded report of all the companies they're assigned to, and you can also have a rollup field on the employee record that list all the companies they are assigned to.
I don't know typically how many employees are assigned to accompany, but if it's a large number, and the selection process is too slow for you as you click the button to add assigned employee, there are ways to speed that up.
