Answers.Body: <p>This is a known issue: <a href="https://issues.civicrm.org/jira/browse/CRM-15682" rel="nofollow">https://issues.civicrm.org/jira/browse/CRM-15682</a></p>
  
  <p>As a bug that affects relatively few people, the core team with their limited resources hasn't allocated someone to investigate and fix this.  If you're a developer or have access to one, this shouldn't be terribly difficult to develop a patch for; alternatively, if you don't have a developer, you may want to submit this to the <a href="https://civicrm.org/paid-issue-queue" rel="nofollow">paid issue queue</a>.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-29T17:19:54.407Z
Answers.LastActivityDate: 2015-08-29T17:19:54.407Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>If you perform an advanced search using the Display Results As Related Contacts feature, the related contacts presented are correct but when you export but the original contacts are exported instead of the related contacts. </p>
  
  <p>I expected that the contacts exported would match the search results, but this is not occurring. Is this correct?</p>
  
Tags: <search>
Title: Why do the exported contacts differ from the contacts presented on the Advanced Search using Display Results as Related Contacts?
ThreadText: # Why do the exported contacts differ from the contacts presented on the Advanced Search using Display Results as Related Contacts?
  
  (Asked by: username_0 on 2015-08-28)
  
  If you perform an advanced search using the Display Results As Related Contacts feature, the related contacts presented are correct but when you export but the original contacts are exported instead of the related contacts.
  
  I expected that the contacts exported would match the search results, but this is not occurring. Is this correct?
  
  **Tags:** search
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-08-29. Score: 2 | Accepted answer
  
  This is a known issue: <https://issues.civicrm.org/jira/browse/CRM-15682>
  
  As a bug that affects relatively few people, the core team with their limited resources hasn't allocated someone to investigate and fix this. If you're a developer or have access to one, this shouldn't be terribly difficult to develop a patch for; alternatively, if you don't have a developer, you may want to submit this to the [paid issue queue](https://civicrm.org/paid-issue-queue).
  
  
  ---
  
  