Answers.Body: <p>In my experience, I default toward relationships, but might use a custom reference field in these situations:</p>
  
  <ul>
  <li>I need to export multiple people with the same relationship.  For instance, if Andy and Beth both have a "Mentor of" relationship to Johnny, you can't export Johnny's record showing both mentors.  So I'll make two contact reference fields.</li>
  <li>You need to create a form where a site visitor needs to specify an existing contact.  For instance, if new members must be referred by existing members, you may want them to be able to submit a profile that indicates who the referring member is.  If you use Webform-CiviCRM Integration, I think you can do this with a relationship, but otherwise, you need a contact reference field.</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-06T18:28:22.087Z
Answers.Text: Awesome, thanks, this is exactly what I was looking for. I'm keeping this open for a while to see what others have to share.
Answers.UserDisplayName: LunkRat
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-06T18:23:22.427Z
Answers.LastActivityDate: 2015-04-06T18:23:22.427Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.Body: <h2>Relationships</h2>
  
  <ul>
  <li>Can be used to give permissions between contacts</li>
  <li>Have a start &amp; end date</li>
  <li>Can attach notes &amp; additional custom data</li>
  <li>Can be displayed as advanced search results</li>
  </ul>
  
  <h2>Custom contact reference fields</h2>
  
  <ul>
  <li>Can be added to a profile form</li>
  <li>Can be displayed in its own tab or section of the contact summary page</li>
  <li>Customizable autocomplete filters for limiting which contacts are selectable</li>
  </ul>
  
  <h2>Both</h2>
  
  <ul>
  <li>Can be added to a (drupal) webform</li>
  <li>Are searchable via advanced search</li>
  <li>Could be the basis of a smart group</li>
  <li>Can be used in a report (although custom fields are in all reports whereas relationships are only in certain reports)</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-07T00:39:28.840Z
Answers.LastActivityDate: 2015-04-07T18:50:30.817Z
Answers.LastEditDate: 2015-04-07T18:50:30.817Z
Answers.UserDisplayName: Coleman
Body: <p>This is admittedly open-ended any may just depend too much on use-case. I am looking for advice on when it is preferable to create a custom <strong>Contact Reference</strong> field instead of just creating a custom relationship. </p>
  
  <p>If you have an example of a situation where you chose one over the other, that would be helpful. </p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-06T20:45:24.937Z
Comments.Text: One thing to keep in mind - maintaining relationships can put a burden on the user/administrator.  For example, setting up for spouses, the way the system is designed, encourages (does not require) a household + spouse A + Spouse B.  I've found there is a lot of overhead / training / automation to manage the household.
Comments.UserDisplayName: Sonicthoughts
Tags: <custom-fields><relationships><architecture>
Title: How to decide between using a custom Relationship and using a custom Contact Reference field?
ThreadText: # How to decide between using a custom Relationship and using a custom Contact Reference field?
  
  (Asked by: username_0 on 2015-04-06)
  
  This is admittedly open-ended any may just depend too much on use-case. I am looking for advice on when it is preferable to create a custom **Contact Reference** field instead of just creating a custom relationship.
  
  If you have an example of a situation where you chose one over the other, that would be helpful.
  
  **Tags:** custom-fields, relationships, architecture
  
  > **Comments:**
  > **username_1**: One thing to keep in mind - maintaining relationships can put a burden on the user/administrator.  For example, setting up for spouses, the way the system is designed, encourages (does not require) a household + spouse A + Spouse B.  I've found there is a lot of overhead / training / automation to manage the household.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2015-04-07. Score: 3 | Accepted answer
  
  ## Relationships
  
  * Can be used to give permissions between contacts
  * Have a start & end date
  * Can attach notes & additional custom data
  * Can be displayed as advanced search results
  
  ## Custom contact reference fields
  
  * Can be added to a profile form
  * Can be displayed in its own tab or section of the contact summary page
  * Customizable autocomplete filters for limiting which contacts are selectable
  
  ## Both
  
  * Can be added to a (drupal) webform
  * Are searchable via advanced search
  * Could be the basis of a smart group
  * Can be used in a report (although custom fields are in all reports whereas relationships are only in certain reports)
  
  
  ---
  
  ### Answer by username_2 on 2015-04-06. Score: 3
  
  In my experience, I default toward relationships, but might use a custom reference field in these situations:
  
  * I need to export multiple people with the same relationship. For instance, if Andy and Beth both have a "Mentor of" relationship to Johnny, you can't export Johnny's record showing both mentors. So I'll make two contact reference fields.
  * You need to create a form where a site visitor needs to specify an existing contact. For instance, if new members must be referred by existing members, you may want them to be able to submit a profile that indicates who the referring member is. If you use Webform-CiviCRM Integration, I think you can do this with a relationship, but otherwise, you need a contact reference field.
  
  > **Comments:**
  > **username_0**: Awesome, thanks, this is exactly what I was looking for. I'm keeping this open for a while to see what others have to share.  
  
  ---
  
  