I searched for a constituent in webview yesterday that turned out to only exist as a relationship record on a different full constituent record.
There was no indication, link to click on, viewable piece of data that told me what full constituent record it was sitting on. This needs to be available!
Since relationships aren't (are no longer?) searchable in the database view either unless they're spouses or contacts for an org record, the only way to figure this out was by running a query to search for it. This is very wasteful of everyone's time!
Please put SOME kind of reference, even if it's only viewable, to tell us what record to go to in order to add actions, notes, assign fundraisers, etc.
Recently, I added a relationship contact (ex John Doe) in database view to an org record, ex: Microsoft, and thought my colleague just hadn't added a relationship, and he is exclusively working in NXT at this point. When I went to search in NXT for John Doe after I added the contact in Database view a second John Doe non-constituent showed up. I then opened this alternate non-constituent record for John Doe and it didn't show where it existed? Back to database view and only the John Doe I added was showing in Microsoft. What a mess this will be if not corrected by the time database view is sunsetted
Non-constituent relationship records in webview are woefully incomplete. We need to be able to see which records they are related to, see their relationship custom fields. Non-constituent records have remained unchanged in webview for years and they really need to be completely realized before database view is sunset.
This is badly needed! For new users who don't know what to look for to differentiate between a full constituent record and a constituent record, it's very confusing. As relationship records don't contain a "Relationships" tile, you can't see which record it lives on. I would like to see a link to the constituent record that the relationship record "lives on" in the header information by the name, like:
Relationship Name
President (Relationship type) at XYZ Company (linked to Constituent record)
I totally agree. I was doing a parent import process in omatic cloud -it gives you the option to review possible relationship matches, but when you jump to the record in RE you can't tell what constituent that non-constituent is tied to as a relationship.
Completely agree - this is a real pain!! I have to run a separate query to look for the relationship name and then try to deduce which record the person is connected to and why. This is especially cumbersome when the person has a very common name.
This would definitely be helpful as we use relationships a lot