This part of FileMaker did not change with the FileMaker 12 release.
Do you have these relationships?
Members::__pkMemberID = Member_Committee::_fkMemberID
Committees::__pkCommitteeID = Member_Committee::_fkCommitteeID
If so, a portal to Member_Committee placed on a Committees based layout will list all committee members--in both FileMaker 11 and 12.
Thank you for your response.
It appears I do have the structure you stated above.
pk_People ---- fk_people_committee_assignment ----- pk_committee
I have made sure the boxes are checked that allow creation of records on both sides of the join table.
The two main differences between the old solution and this one are: I am using the data separation model and a UUID in my people (or member) table. Otherwise the everything else seems to be exactly the same.
I see a key difference. You have only one foreign key field in the join table, people_committee_assignment matching to primary key fields in both people and committee. There should be two foreign key fields in the join table--one to match to each primay key in people or committee.
Sorry I left that out. I actually do have two foreign keys. So it really looks like this:
pk_People ---- fk_people_committee_assignment
Then this should work.
If it does not, check the table occurrence and field names for your portal and the fields within it.
If you plan on editing your committee assignments, this should be a portal to the join table. If you just need a "read only" list of committee members, it can be a portal to People.
What is interesting is that I can see fields in the Committee TO from the People Layout, but I cannot see fields in the People TO from the Committee Layout. I hope that makes sense. So the relationship works in a unidirectional fashion, but not bidirectional.
I hope that might help in finding why the relationship isn't working.
That suggests that your portal or fields in the portal on your Committee layout is/are not specified correctly.
I am pulling my hair out trying to get these specified correctly. I am not sure where this is breaking down. I even tried creating just this simple relationship in a test database and from the People (parent) table I can see info from the committee assign (join table) and the committee table (parent); on the join table I can see info from both parent tables, but cannot see anything on the committee table from the other two tables. I am uploading a screen shot of my test relationship. I feel like I am missing something simple but the aha moment hasn't hit yet.
I am suggesting that you look at your layout settings, not the relationships graph.
You might also compare what you have to this demo file I share for those working with many to many relationships. You can convert it to FileMaker 12 format by selecting Open to open it from the File Menu: https://www.dropbox.com/s/oyir7cs0yxmbn6i/ManyToManywDemoWExtras.fp7
Tweaking the layout was the trick. Not sure exactly what I did, but I tried putting a portal on another layout based on the same TO and everything started to work the way it is supposed to.
Thank you very much for your help.