Hi Mike :)
Auto populate is so they automatically fill vs having to select a limited drop down list.
I was able to get that to work using Marks suggestions about 10 min ago.
The reason for it - is to ensure that all the items that are related to that employees assignment gets logged to the Employee File. So an employee could have had 5 assignments - I want to be able to view all items associated with those assignments under the Employee file, vs having to go to each assignment to view them.
Having them linked to the project, then also lets me know what the project was incase it was a particularly difficult project, and they did poorly on that one project or excelled on another, we can take those things into consideration when reviewing the employee file as a whole.
The other thing I have set up is assigning a supervisor to each employee Assignment. This way it limits who has access to that employees details. In addition to a Project Supervisor as well.
Having these split, allows access to review trends for the particular project across all employees that worked that project with out having to drill down into the assignments themselves. And it allows the Assignment supervisor to review their active employees and develop them easier.
I hope this helps :)
For the pipeline trigger, that sounds like a feasible option as well. I will have to look more into that. The QB App that I am developing is all focused on employee development, metrics etc. so linking the various tables to the employee file through the assignments table is going to be a very common item.
------------------------------
Amber Anderson
------------------------------