Mike Olson - 11 years ago
What you can do is create a third custom object, called something like, "LabProjectEmployees." Make it have the LabProject object as its master in a master/child relationship. Then, on the LabProjectEmployees object, you create an employee lookup field, and a role picklist. Then, you can tie any number of employees in any number of roles to a given Lab Project.
It's similar to contact roles for an account or partner roles for an opportunity.
Anyway, I'm promoting your idea.
Ted Chapman - 12 years ago
The above wouldn't solve my similar problem. I need to represent contacts with their (many) related contacts. I use a relationship object to handle the job but am left with 2 Related Contacts lists on the Contact page, which is very confusing for people. I am going to try to handle this using Visualforce, hopefully that will solve the problem without also creating duplicate rows.
Christoph Knoch - 12 years ago
maybe I missunderstood you. But maybe my english wasn't good enough. I do have a similar object and for each assigned project memger I add a new Projektteammember with one role. Then I enter the next teammember with one role and so one. This way I can add unlimited Employees with different roles to an object. I could send you a screenshot fo this, maybe this makes it easier?
Matthew Lamb - 12 years ago
Thanks for the comment nbanas, glad to know someone else has the same use case! One workaround is to add a junction object between the Lab Project and Employee objects, but then the process of adding Employees to the Lab Project gets longer (more clicks to add). Especially considering that 99% of the time (in my scenario anyway) there are never more than 2 Employees on any given Lab Project.
Nathan Banas - 12 years ago
My organization is experiencing similar issues. We have a custom object called 'server' which tracks all server information for our Engineers (ie. last patch date, decommission date, OS installed, and some of the software installed on this server just to name a few fields). We recently received a request to create a way of tracking security scans of these servers and the requestor wanted the ability to assign up to 10 servers per scan rather than having one scan record per scan. The requestor also wanted a related list on the server to show all of the scans, the scan status (pass/fail), and when the scan took place. Via a custom object we can add 10 lookup fields to our server object, but in turn this would be 10 related lists on the server object. The ability to merge these related lists into one Security Scan list would be extremely helpful to compact the display of this information for our Engineers to review.
Matthew Lamb - 13 years ago
I'm not completely sure I follow you. With only one custom object lookup, how can you support assigning multiple people to a project? And if the 'Role' drop-down gets placed on the Employee object, you lose the ability to change roles (and track the changed roles) between projects, right? Thanks!