Don't see any need for two pairs of match fields. They appear to do exactly the same thing.
If your layout is based on Yearly Compensation, The relationship shown--even if modified to use only the first pair of match fields, will have no effect on what Yearly Compensation records are currently visible on your layout. The relationship, instead, will control what data from Personnel can be shown on your layout.
If your layout was based on Personnel Records, a portal to Yearly Compensation would list all Yearly Compensation records associated with the current employee. But this is not ideal for printing.
A list view layout based on Yearly Compensation makes sense for printing, but you have to take steps to pull up a found set of the specific records that you want to print. You can use a script to perform a find or use Go to Related Records from the Personnel Layout to pull up specific Yearly Compensation records for your report.
I'm definitely struggling with controlling what data from Personnel can be shown. Here is what it looks like, and the grey bar is where it should be sorting by employee;
Can you get the right results using a SQL statement?
I always try to make sure whatever I'm asking FM to do is "Query-able" first.
P.S. I like Phil's suggestion of trying GTRR - that command (script step, or whatever) alone makes FM easy to navigate.
I can't tell anything from your screen shot of a layout taken while in Browse Mode. Nor do I understand what you are trying to tell me about the "grey bar".
I suggest that you show a screen shot of your relationships and then explain what parts of the above screen shot are fields from the Personnel table and whether you are or are not using a portal. From what I see, a portal to Personnel would not make any sense on a layout based on Yearly Compensation.
My apologizes. I'm not actually trying to create a portal in any sense, but display the records entered into the yearly compensation portal on another layout. The only field that is from the Personnel is FirstLast, which is in the "grey bar", or subsummary when sorted by Personnel Records::FirstLast.
EDIT: please ignore the g in fields marked as g_ComSum and so forth. It does NOT mean they are global fields.
If the field does not show any data, then you have a record in Yearly Compensation that either does not match to any records in your Personnel Records or you have a record in Personnel where this field is empty.
Better check the data in your fields.
And I will repeat that you do not need two pairs of match fields in this relationship. It's possible that the extra pair of fields is why you are having this issue as it may keep records from matching that should match.
I got it working correctly, thank you for your help! What I did was get rid of the second match field, and instead of use Personnel Records:: FirstLast, I separated the two and used a merge field. I then changed the report parts to subsummary when sorted by Last Name(Leading) and subsummary when sorted by Year(Trailing). I then sorted by Last Name and then year in an ascending order. This returned all portal records per employee, sorted them alphabetically, and put the compensation info in chronological order.