Seems like your layout is functioning exactly as you have designed it to function, just not as you want it to function.
I would guess, (there's a lot you don't tell us about your database design that might affect how this works), that you need to remove the field from Body Parts from the Sub Summary layout part and replace it with Cs::body part name. You could also place a one row filtered portal to Body Parts with the same type of filter expression used with the other portals in the sub summary layout part.
Precisely!I expected the first sub-summary to display each client name and this works as expected. I expected the second sub-summary to then display each body part name. and this does not work as expected.I've attached the design. Basically the question would be how do I get each body part name to list in the sub summary?
It looks like your layout is based on the wrong table, but given that you are using a cartesian join here, it's not clear if your current data model will even support such a report design as you are trying to set up.
If you had this data model:
Clients::__pkClientID = Client_BodyPart::_fkClientID
BodyParts::__pkBodyPartID = Client_BodyPart::_fkBodyPartID
Then you could set up such a summary report by using a layout based on the Client_BodyPart layout and still be able to include fields from Clients and BodyParts.
For an explanation of the notation that I am using, see the first post of: Common Forum Relationship and Field Notations Explained
Thanks for the clarification! I was trying to avoid creating the "Invoices" scenario that you reference.
I ended up taking your advice though, and changed the basis of the layout Body Part Risk from Client to Body Part. I have a separate table that holds some global fields. I was able to use the gClientID field from that table as the filter for the portals.
This creates the layout I was expecting. Thanks again!