Export selected fields doesn't export related contacts if related info is present in mapping

Steps to replicate

• Search > Find Contacts
• Click the Search button > results in X contacts
• Select All contacts
• Actions > Export Contacts
• Use Export PRIMARY fields, all X contacts are exported
• Now try Select Fields for Export with some fields as related fields like employer, spouse of id etc
• DO NOT MERGE
• Export > only X-N contact records where N is the contacts that appeared in related contacts fields

I replicated this on dmaster and seems to be a regression when compared it with 4.7 site where no. of contacts exported was X regardless related fields are used in mapping or primary fields are used.

@eileen thoughts?

changed the description

Linking for cross-ref purposes: #1342 (closed). Not sure if it's exactly the same, but same idea where some related contact records get left out. I haven't looked any further into that ticket.

changed the description

added regression label

Let's tag as a regression until we rule that out. Looks like an inner join or a WHERE that has the same effect

@yashodha I just tried to replicate this with the mapping per image but all 64 contacts exported - can you narrow down how to replicate?

CiviCRM_Contact_Search__5_.csv

@eileen the key piece here is include Parent of Contact Id

I was able to replicate on dmaster with Spouse relationship and contact id for spouse. If you omit contact id for related contact, the row count is correct.

Export these 2 contacts:

Export PRIMARY fields

Both rows exported

Select Fields to Export

Only 1 row

Ah - I wonder if id is leaking

@eileen I suspect it is.

mentioned in commit 69edd19f

mentioned in commit 7b1b3302

Merged into 5.26 via https://github.com/civicrm/civicrm-core/pull/17462

closed

changed milestone to %5.26.0