When the Contact field is not checked in DB view, then the Relation Contact Primary Addressee is not populated in a query result even though the person is setup as the Contact through Web view Relationship. This is a defect in Web view and I believe it needs to be fixed.

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.

Impact:

• 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.

Yes - I was recently working on a "how to add a contact to an organization" for staff working exclusively in web view ... and was surprised to find this. (and also cannot have anyone in web view add a contact until either this is fixed, or we have to change how we do things.)

{"children":[{"type":"paragraph","children":[{"text":"Agreed that this is definitely needed. Adding a Contact Type of Primary does not trigger the same options as the check box "}]}]}

Yes please! We really need this as currently none of our fundraisers can add primary contacts easily.