1 of 1 people found this helpful
The portal filter for each tab would be:
Leader tab -> ProjectParticipation::As = "project leader"
Assistants tab -> ProjectParticipation::As = "project assistant"
You're many-to-many relationship seems to be sound based on your description. But there might be issues in how you've set up record creation.
Usually I do not allow record creation through relationships in many-to-many cases. I would create a script that grabs __pkProjectID as a variable $id, goes to a layout based on ProjectParticipation, creates a new record, and sets _fkProjectID as $id. Then you can use a popup or drop down list of __pkContactID and Name (show values from second field only), to select the contact, and another drop down to select the role.
After you've created this, you can have a "complete" button that takes them back to the main project layout. You can attach validation and cancellation procedures to this complete button.
Thanks for the reply.
Had made errors in the portal configuration. Had accidentally selected the wrong table, under "View records as the relationship." Do not know how.
I was stuck in the idea that the fault must lie in the "Filter portal records"
Your answer helped me to see the big picture.
Glad to hear,
ERDs and talking out relationships as sentences in your head usually helps me out.
Did you know you can print the relational diagram out? Very useful when looking at complex relationships.