Allow multiple contact types on a relationship record

In many companies, one person would have multiple contact types. Using a primary doesn't really meet the need either. In large companies we would have a primary, often the funding contact. But then that person might also be a contact for the bowling and golf, but not for volunteers or Hall of Fame. Currently we have to add the relationship record multiple times. It makes for a messy data list and doesn't seem to logical for a relational database.
  • Guest
  • Jun 29 2015
Organization Name (Please enter full organization name)
Reported Version
  • Attach files
  • Becky Kimball commented
    April 25, 2016 19:52

    Hi, just wondering if this idea is still under review by Blackbaud. Would be happy to discuss reasons why this is so important.

  • Guest commented
    May 11, 2016 09:36

    The primary tick box is really confusing for end users, as they tend to make an assumption of what primary means for them. If there is no better way to describe what primary really means, it may be better to remove it.

    We would also like to use the contact type more, but are concerned about the single use only and we will not compromise on our data integrity by creating multiple relationship records (albeit it is a good workaround).

  • Guest commented
    December 2, 2016 01:57

    Being able to have unlimited contact type assignments would be really valuable for us as well. Multiple relationships is not an option for us as it causes data integrity issues.