Is Contact selectively appears in web view

When setting up relationships in database view a individual relationship to an organization can be marked as "Contact" - and no contact type assigned. When this is done from web view on the relationship (when you select edit relationship) - there is a checkbox right above "Primary employement for <name>" that's called "<Name> is a Contact for <Org Name>".


If you try setting up the same relationship in web view that checkbox does not exist or appear. And you must choose a contact type to make the relationship a contact of the organization. But even removing contact type later on, doesn't cause the "Is Contact" box to appear.


So this seems limited to relationships that are only created in database view. We would like this fixed as we don't want a contact type to be used on many relationships.

  • Matt Haynes
  • Jul 2 2024
  • Reviewed: Voting Open
  • Attach files
  • Emily Marshall commented
    18 Aug 16:15

    Currently, when adding a relationship to an organization in Web View, the checkbox that designates the relationship as a Contact is not available. As a result, users cannot create a relationship that is flagged as a contact directly from Web View.

    I have observed that if the relationship is created or edited in Database View and the Contact checkbox is selected, that designation is visible in Web View. However, there is currently no way to initialize that checkbox within Web View itself.

    Creates inconsistent functionality between Database View and Web View.

    Requires users to switch to Database View to complete what should be a standard relationship-management task.

    Slows down data entry and may lead to incomplete or inaccurate contact designations.