Answers.Body: <p>We are having the same problem with relationship imports that have custom subtypes.  Our subtypes are Individual - Student and Organization - School.  The relationship is Student of (Student) - Student for (School).</p>
  
  <p>The relationship does not show up for mapping during import.  My testing shows that it's the first part (a) that causes it not to show up.  If the (a) is changed to Individual it will show up, all other combinations do not.</p>
  
  <p>I have also verified that this relationship does show up in 4.5.4.  This is the only 4.5.x version I could readily test with.  I have verified on the demo test as well.</p>
  
  <p>I have created an issue: <a href="https://issues.civicrm.org/jira/browse/CRM-17544" rel="nofollow">https://issues.civicrm.org/jira/browse/CRM-17544</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-10T17:48:42.190Z
Answers.LastActivityDate: 2015-11-10T17:48:42.190Z
Answers.UserDisplayName: EHendricks
Body: <p>We have an import that we do a few times a year that I set up about 2 years ago.  Until today, it's never had an issue.  We are using v4.6.3, and the last time we did it we were using a 4.5.x version.</p>
  
  <p>When importing households, we have some custom relationships defined.  They are Individual to Household relationships. These relationships do not show up in the selector for the mapping the imported data.  Some relationships DO show up; Household member and Head of Household, plus two other relationships in which contact a type is not set.</p>
  
  <p>The relationships that don't show up are useable in all other contexts that I have tried.  They are enabled.  I have gone so far as to compare the relationship type records in mysql and I see no obvious issues.</p>
  
  <p>I've also searched the Jira to see if there's a known issue but I don't see any.</p>
  
  <p>Suggestions?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-08-12T23:43:34.193Z
Comments.Text: I have duplicated this on the demo.civicrm.org site.  The relationships do not show up during Import when they are a "subtype" of household. So:
  
  Create a subtype of household "Household subtype";
  Create a relationship where type "a" is Individual and "b" is the new subtype above;
  Import a csv for Household, select the subtype.  On the next page you will not be able to select the new relationship type in order to designate an identifier.
Comments.UserDisplayName: Rob Brandt
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-08-13T00:47:17.350Z
Comments.Text: Rob do you want to confirm if this is an issue only related to Households? Ie do the subtype options show if you were importing where Contact A and B were both Individuals?Households don't get used as much so perhaps it missed out on some code/love.
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-08-13T16:47:23.197Z
Comments.Text: Well, shoot.  Now I can't replicate the problem.  I tried adding subtypes for each main type, then adding relationships between each type and new subtype (9 in all) and all 9 worked.  Any chance this was fixed last night?  The demo does say it's running 4.6.7.
Comments.UserDisplayName: Rob Brandt
Tags: <import><relationships><households>
Title: Relationships not available on household imports
ThreadText: # Relationships not available on household imports
  
  (Asked by: username_0 on 2015-08-12)
  
  We have an import that we do a few times a year that I set up about 2 years ago. Until today, it's never had an issue. We are using v4.6.3, and the last time we did it we were using a 4.5.x version.
  
  When importing households, we have some custom relationships defined. They are Individual to Household relationships. These relationships do not show up in the selector for the mapping the imported data. Some relationships DO show up; Household member and Head of Household, plus two other relationships in which contact a type is not set.
  
  The relationships that don't show up are useable in all other contexts that I have tried. They are enabled. I have gone so far as to compare the relationship type records in mysql and I see no obvious issues.
  
  I've also searched the Jira to see if there's a known issue but I don't see any.
  
  Suggestions?
  
  **Tags:** import, relationships, households
  
  > **Comments:**
  > **username_0**: I have duplicated this on the demo.civicrm.org site.  The relationships do not show up during Import when they are a "subtype" of household. So:  Create a subtype of household "Household subtype"; Create a relationship where type "a" is Individual and "b" is the new subtype above; Import a csv for Household, select the subtype.  On the next page you will not be able to select the new relationship type in order to designate an identifier.  
  > **username_1**: Rob do you want to confirm if this is an issue only related to Households? Ie do the subtype options show if you were importing where Contact A and B were both Individuals?Households don't get used as much so perhaps it missed out on some code/love.  
  > **username_0**: Well, shoot.  Now I can't replicate the problem.  I tried adding subtypes for each main type, then adding relationships between each type and new subtype (9 in all) and all 9 worked.  Any chance this was fixed last night?  The demo does say it's running 4.6.7.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2015-11-10. Score: 2
  
  We are having the same problem with relationship imports that have custom subtypes. Our subtypes are Individual - Student and Organization - School. The relationship is Student of (Student) - Student for (School).
  
  The relationship does not show up for mapping during import. My testing shows that it's the first part (a) that causes it not to show up. If the (a) is changed to Individual it will show up, all other combinations do not.
  
  I have also verified that this relationship does show up in 4.5.4. This is the only 4.5.x version I could readily test with. I have verified on the demo test as well.
  
  I have created an issue: <https://issues.civicrm.org/jira/browse/CRM-17544>
  
  
  ---
  
  