Thank you Hilary, you sent an explanation offline and I want to make sure others can find the solution if needed. I took you suggestion of moving the secondary data connection query and rules from the secondary AccountID field to the Main data field created to keep up with the Account ID (I named it AccountIDLookup). Anyway, I don't understand why it works in one form and I had to make this change in this form, but it works, so thank you.
Below is the text you sent to me offline for Forum readers' benefit:
The issue is that you run the query and set the fields on
the change of the account name in the data connection. If you have a repeating
structure, and you set values from a rule on a node outside of the repeating
structure, you’ll set all instances.
Remove
the rules on the secondary data connection query field. Put them here instead:
Set the account name query field, execute the query, then
when you set the name and email you know it is the one for that group (although
since I see Sect_PeoplePickers is not repeating, perhaps I still don’t
understand what you are trying to do or what the issue is). I do see this is
also how the other form is set up, but since these parent groups aren’t
repeating, I am not understanding how the Conference Briefing Center form
corresponds to your post? Maybe send a screenshot of the filled out form
showing the issue.
The pc:Person group will always show in the schema as
repeating – because the people picker can be set to allow multiple entries in
the control. H.