Answers.Body: <p>Thanks Paul - it turned out that relationships needed to be set up at contact type level, not as a contact sub type in order for the relationships options to be displayed in the import screens.</p>
  
  <p>So where contact sub types had been set up on earlier versions of civi, the relationship had to be changed to conctact type leve i.e</p>
  
  <p>individual to individual
  not Individual (parent) to Indiviudal (child)</p>
  
  <p>The relationship names can stay the same just not the level.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-24T12:24:17.080Z
Answers.Text: IMO that is a bug and you should consider reporting.
Answers.UserDisplayName: Sonicthoughts
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-22T14:34:58.470Z
Answers.LastActivityDate: 2015-07-22T14:34:58.470Z
Answers.UserDisplayName: Catherine
Body: <p>I have a set of custom relationships I need to import against, but the import mapping dropdowns are only showing the three default relationships:</p>
  
  <p>Employee of..
  Family member is..
  Household member is..</p>
  
  <p>Any ideas?  I cannot see any options on the custom relationship settings i need to change. We are using CiviCRM 4.6.2 (recently upgraded)</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-06-23T16:20:36.170Z
Comments.Text: What shows up in the drop down is determined a bit by rather or not you importing households, individuals or organizations and what the custom relationship apply to, e.g. individuals.  If you aren't already, you might import the contact and then do a second pass for the relationship and do update.  Also, try reversing what your adding the relationship to.  For example, if you're trying to import an individual as part of household, try importing update the hh and add the ind as a hh member
Comments.UserDisplayName: Paul-Tahoe
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-07-15T16:29:56.543Z
Comments.Text: Thanks Paul   - it turned out that relationships needed to be set up at contact type level, not as a contact sub type in order for the relationships options to be displayed in the import screens
Comments.UserDisplayName: Catherine
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-07-15T17:34:50.667Z
Comments.Text: Catherine if you want you can put what you wrote as an answer.  That way other people who trip across the same thing will have an answer.  You might elaborate on exactly how you were trying to import and what you did to fix it.
Comments.UserDisplayName: Paul-Tahoe
Tags: <import><relationships>
Title: Importing relationships
ThreadText: # Importing relationships
  
  (Asked by: username_0 on 2015-06-23)
  
  I have a set of custom relationships I need to import against, but the import mapping dropdowns are only showing the three default relationships:
  
  Employee of..
  Family member is..
  Household member is..
  
  Any ideas? I cannot see any options on the custom relationship settings i need to change. We are using CiviCRM 4.6.2 (recently upgraded)
  
  **Tags:** import, relationships
  
  > **Comments:**
  > **username_1**: What shows up in the drop down is determined a bit by rather or not you importing households, individuals or organizations and what the custom relationship apply to, e.g. individuals.  If you aren't already, you might import the contact and then do a second pass for the relationship and do update.  Also, try reversing what your adding the relationship to.  For example, if you're trying to import an individual as part of household, try importing update the hh and add the ind as a hh member  
  > **username_0**: Thanks Paul   - it turned out that relationships needed to be set up at contact type level, not as a contact sub type in order for the relationships options to be displayed in the import screens  
  > **username_1**: username_0 if you want you can put what you wrote as an answer.  That way other people who trip across the same thing will have an answer.  You might elaborate on exactly how you were trying to import and what you did to fix it.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2015-07-22. Score: 3 | Accepted answer
  
  Thanks Paul - it turned out that relationships needed to be set up at contact type level, not as a contact sub type in order for the relationships options to be displayed in the import screens.
  
  So where contact sub types had been set up on earlier versions of civi, the relationship had to be changed to conctact type leve i.e
  
  individual to individual
  not Individual (parent) to Indiviudal (child)
  
  The relationship names can stay the same just not the level.
  
  > **Comments:**
  > **username_2**: IMO that is a bug and you should consider reporting.  
  
  ---
  
  