I'm guessing that you have this relationship:
Projects -------<TeamRole>------- Employees
So that TeamRole is a "Join" table listing the team of employees assigned to a given project and documenting their role on the team for that specific project...
I suggest to stick with the filtered portal approach with a filter expression set for each such one row portal. The alternatve you describe can be used, but requires defining special calculation fields and added table occurrences so that you can set up "role specific" relationships for each column. That's how we used to do this (and still do when working with older versions) before portal filtering was added in the release of FileMaker 11.
Here's how you would set up just the column for Project Manager:
Define a calculation field in projects: constProjectManager. Make "Project Manager" the sole term in its calculation.
Use the duplicate button (two green plus signs) in Manage | Database | Relationships to make a copy of TeamRole.
Set up this added relationship:
Projects::ProjectID = ProjManagerTeamRole::ProjectID AND
Projects::constProjectManager = ProjManagerTeamRole::Role
Define a calculation field, cMemberName in TeamRole to evaluate from the context of team role as Employees::Name
Now you can add ProjManagerTeamRole::cMemberName to your projects report layout to list the project manager. You'll need to add a const field and an additional relationship for each such column on the report. See why a filtered portal is easier? (You can hide the boundaries of your portal so that it looks like any other field on your layout.)
Thanks so much PhilModJunk!
I wanted to make sure I was doing things the right way and wasn't sure the filtered portal approach was correct. Now i can easily finish the report.