RE Database view does not allow user to directly search for a non-constituent record, so that is fine. However, since unified view now allow user to perform such a search, it only makes sense to have relationship section to show how this non-constituent record is related to the constituent records, regardless of past or present

Yes, somewhere on the non-constituent record should be the information about the which constituent(s) the non-constituent is linked to. There are of course multiple additional steps we can take to find out if it is an org contact, tribute acknowledgee, non-spouse relationship, etc., but it is perplexing why this basic request of having a link back to the related constituent isn't directly available. This is especially important since the workarounds primarily require switching over into DB view.

fundamentally this request is to make the relationship tile visible on non-constituent records.

This is one of the most frustrating things in webview. Simply having a relationship tile in non-constituent records with a direct link back the parent record (parent record meaning the full constituent they are connected to, not a familial relationship) would solve this issue and make managing records much simpler and would avoid confusion from gift officers who are tech adverse.

It is helpful for no one to be unable to see the non-constituent's relationship to a full constituent when you navigate to their non-constituent record. Additionally, once in a non-constituent record because there is no direct link to their relationship, you also cannot get back to the main constituent's record without searching for them again. It's extremely inefficient and frustrating.

It is very difficult to look at any non constituent in webview currently. I was sent a direct link to a non constituent record today, and found myself struggling to figure out who on earth it was, and what constituent they were related to, and had to resort to searching/querying.

This is very inefficient, and this information is integral to the existence of the record itself. A non constituent relationship record on an org would be created specifically because they are related to the organization. Going to the non constituent and not being able to see what organization they have a relationship to, if they are a contact, the relationship/reciprocal information, etc is a huge limitation.

100% need to be able to know what Constituent Record a relationship sits on. It is hindering to not be able to click through to the Constituent or even know which Constituent it pertains to. When you have common names there can be several Robert Smiths and not knowing who they are related to makes things extremely difficult to include in the proper lists, queries, etc.

This would be SO helpful! I want to search for possible relationships to make sure I'm not duplicating a record, and if I find John Smith as a non-constituent when adding a relationship to Jane Smith, let's say, I have to run a query to see who John is linked to. It's a lot of extra work just to see who this person may be linked to. A person or corporation?

Agreed. It is surprising that vital information for non-constituent organization contacts is absent in web view. You can't even tell who they work for, and the relationship type is missing, i.e., employee, member, etc. This is vital information for our fundraisers. A street address as the only information is not satisfactory. It is vital that all data regarding business contacts from database view be translated over to web view. Otherwise, what is the point of NXT if people have to keep going to back to database view?

We use the Constituent Attributes to identify which Constituent Contacts (at Orgs) are report recipients - reports do NOT always go to the Primary Contact, or they go to more than one person at the org. Address Processing allowed us to filter report recipients.

Possibly I'm behind the curve here, but is it not possible to create non-constituent records in web view? Because I'm not seeing how...

Honestly, if there was just a drop-down relationships tile within the non-constituent record, that should get us there most of the time!

To add a test case, I just looked up a non-constituent individual relationship in NXT where the address was different from the constituent's address. I ended up having to query on the individual relationship import ID to find the record in database view so I could see who the constituent was.

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.

This absolutely needs to happen! Looking up constituents in webview and finding many relationship records but then no idea who it is connected to. Would be amazing to have a link to the connected constituent at the very least! Suggestions from original post would all be great!

This is an absurdly easy fix. I would also like to see the relationship attributes.

From a code and functionality perspective, this could operate exactly how the Spouse relationships display on an individual's record - when viewing a non-constituent contact, you could always click back to the parent record. 

For those non-constituent contacts that are linked to more than one parent record,  adding the "Relationships" box  to non-constituent records would also solve this problem.  

Yes, it is important to include this source info when the search is done. So  it is clear whether a new record needs to be added. Or else resulted into lots of duplicate records.

The most essential piece of missing information is the source record. For a non-constituent relationship record, it is possible to search for and open it in web view, but from there, no way to know what the source record is for the relationship. 2 EASY fixes:

1) Display the source record as a column in the search window when you search for relationship records. It currently displays only Name, Preferred address, Constituent ID, Alias, Former name, Preferred name, Spouse name, Contact for.

Note that the "contact for" column would solve the issue if the relationship were marked as a contact. So you only need to display source record in the same way.

2) Display the source record within the relationship record itself.

Please fix! This is an easy solution that would solve a TON of usability issues!

Surely this is a pretty basic fix / requirement.  Can we get it done soon please?

Also listed as https://renxt.ideas.aha.io/ideas/RENXT-I-1768