Portal quit working

[John Chamberlain]

I have a portal that was showing multiple records just fine. This page tracks donations made to a non-prof, and when a donor name is chosen, it finds the correct number of records, but the portal only shows the first record. Also a summary field, which previously had shown the total of all records, now only show the value of the first record.

All fields are inside the first line of the portal, and the portal is defined as 1 row with 20 repetitions and a scroll bar.

Can anyone suggest what happened here?

TIA

[mr_vodka]

did you change the relationship or the base table occurrence for the portal?

[John Chamberlain]

No I didn't - I am attaching a fragment of the file with only one person in it, if you would care to look.

FixNation_DB_copy.fp7.zip

[mr_vodka]

uhmmm cant open the file without an account.

[John Chamberlain]

Sorry, use Gracie

[John Chamberlain]

And user name John

[mr_vodka]

Your layout is based on Donations.

Your portal is based on Personal~Organization Data.

Your fields in the portal are from Donations.

It will only show you the current Donation info...

[comment]

Note also that the relationship's matchfields are incorrect: there is a unique serial ID field on the child side, but not on the parent side - it should be exactly the opposite.

[John Chamberlain]

Please bear with me - I am trying to transition from FMP 6 and earlier to FMP 7, and I am struggling with concepts.

I don't understand what the following means:

"Your portal is based on Personal~Organization Data. Your fields in the portal are from Donations."

Nor do I get what the following is all about:

"the relationship's matchfields are incorrect: there is a unique serial ID field on the child side - it should be exactly the opposite"

Can you please make this a little easier to understand for and old-timer like me?

[comment]

A portal is defined to "Show related records from: [child table]". A portal should be placed on a layout of the parent table, and the fields in the portal should come from the child table. This, BTW, was equally true in version 6 - except the tables were files.

On second look, I think it's not your matchfields that are reversed, just the choice of the layout and of the source table for the portal.

FixNation_DB_copy.fp7.zip

[John Chamberlain]

I think I get it - the layout belongs to Personnel (parent)table, and the portal gets data from the Donations (child)table.

Thanks for your patience.