We use the relationship attributes frequently for non-constituent relationships (and some constituents), especially in a circumstance where the individual shouldn't get their own record (child / minor, work assistant, etc).
We use the relationship attribute to further define an individual relationship to an organization and how we are to interact with them. We use relationship attributes to define which mailings they are to be on - for example one may be on holiday invitation and 5K walk sponsorship request and another relationship may be just holiday invitation. This helps us with pulling the right contact information when needed. Utilizing relationship attributes helps us keep things organized. Without relationship attributes we would have to store this information outside of the database - which is not preferred.
Just announced today by Blackbaud is the retirement of attributes in database view in January 2026 - so can you please move this to planned and ship before then???????
I echo what other has mentioned. We already have tons of data store under the related individual Attributes/Notes section. It doesn't make sense that NXT does not have an screen to display it
Like others as I try to do my work in NXT I am finding that many of the functionalities are missing that are available in DBV. I don't understand how BB can even talk about sunsetting DBV until we can do the same things in NXT that we can do in DBV. This being one of them. We use relationship attributes and need them moving forward.
I also find that - I am finding that the more Blackbaud pushes the idea that they are sunsetting RE NXT database and pushing for full RE Webview use, the more features I find that are going to critically impact our data.
I am currently working with an organization to clean up their contact records, and it is important to know what Relationships are going to look like in webview before we determine how they should be configured.
I find it really odd that there is a Notes field on a relationship in database view that does not display in webview. Yet I can add a summary note to a Relationship in webview - which happens to be a non-constituent - and it does not write back to the Notes field in database view.
Relationships are a big part of fundraising, and it seems like this should have been prioritized when Blackbaud "built webview with fundraisers in mind."
I am finding that the more Blackbaud pushes the idea that they are sunsetting RE NXT database and pushing for full RE Webview use, the more features I find that are going to critically impact our data. There are thousands of relationship records where - especially in light of the fact that RE NXT charges by # of constituents - we do NOT want to create a constituent record because a relationship record on a constituent is more efficient and all that is required. It is imperative, however, that we have a place to enter ATTRIBUTES (especially for organizations to identify which individuals should be on specific lists, eg. events, reports, etc.) AND that there is a place for notes about that person. Not generally long notes, but explanations of the individual's relationship to the organization, or obituaries for deceased family members. We use this information regularly, and rely on it...
We track relationship constituent information in NOTES and ATTRIBUTES. This is especially critical for non-constutuent relationships!!! NOTES - add employment information, family information, obits, etc.
This idea was first entered years ago but our organization just transitioned to NXT in the summer of 2024, so it is a surprise that it has not been addressed. Visibility of the RE spouse attributes in NXT should be the norm and not an exception. Non-constituent spouse attributes are used heavily in RE and are relied upon by our fundraisers who must be able to see these in NXT. Now we must face the decision whether to undertake a big project by moving the spouse attributes onto the constituent attributes, which is not desirable. We shouldn't be forced to find workarounds for NXT and use fields in matters for which they are not intended.
I agree - relationship attributes are very important, particularly those for organisation contacts which are used for a number of purposes, including filtering in queries, exports and mail.
Please make this viewable in NXT. We store a lot of information in attributes for spouses and children who should not be full records. So frustrating not to be able to see this in the web view.
I can't believe that this does not show! Our database is primarily parents and we store all of their children's education and class year information in the attributes. I just did a massive cleanup of these records and it is invisible in NXT. PLEASE MAKE THE ATTRIBUTES & NOTES VISIBLE!!!
We use non-constituent attributes a lot. Please don't get rid of this feature.
We use the relationship attribute to further define an individual relationship to an organization and how we are to interact with them. We use relationship attributes to define which mailings they are to be on - for example one may be on holiday invitation and 5K walk sponsorship request and another relationship may be just holiday invitation. This helps us with pulling the right contact information when needed. Utilizing relationship attributes helps us keep things organized. Without relationship attributes we would have to store this information outside of the database - which is not preferred.
Just announced today by Blackbaud is the retirement of attributes in database view in January 2026 - so can you please move this to planned and ship before then???????
I echo what other has mentioned. We already have tons of data store under the related individual Attributes/Notes section. It doesn't make sense that NXT does not have an screen to display it
Like others as I try to do my work in NXT I am finding that many of the functionalities are missing that are available in DBV. I don't understand how BB can even talk about sunsetting DBV until we can do the same things in NXT that we can do in DBV. This being one of them. We use relationship attributes and need them moving forward.
I also find that - I am finding that the more Blackbaud pushes the idea that they are sunsetting RE NXT database and pushing for full RE Webview use, the more features I find that are going to critically impact our data.
I am currently working with an organization to clean up their contact records, and it is important to know what Relationships are going to look like in webview before we determine how they should be configured.
I find it really odd that there is a Notes field on a relationship in database view that does not display in webview. Yet I can add a summary note to a Relationship in webview - which happens to be a non-constituent - and it does not write back to the Notes field in database view.
Relationships are a big part of fundraising, and it seems like this should have been prioritized when Blackbaud "built webview with fundraisers in mind."
I am finding that the more Blackbaud pushes the idea that they are sunsetting RE NXT database and pushing for full RE Webview use, the more features I find that are going to critically impact our data.
There are thousands of relationship records where - especially in light of the fact that RE NXT charges by # of constituents - we do NOT want to create a constituent record because a relationship record on a constituent is more efficient and all that is required. It is imperative, however, that we have a place to enter ATTRIBUTES (especially for organizations to identify which individuals should be on specific lists, eg. events, reports, etc.) AND that there is a place for notes about that person. Not generally long notes, but explanations of the individual's relationship to the organization, or obituaries for deceased family members.
We use this information regularly, and rely on it...
We track relationship constituent information in NOTES and ATTRIBUTES.
This is especially critical for non-constutuent relationships!!!
NOTES - add employment information, family information, obits, etc.
Any movement on this?
This idea was first entered years ago but our organization just transitioned to NXT in the summer of 2024, so it is a surprise that it has not been addressed. Visibility of the RE spouse attributes in NXT should be the norm and not an exception. Non-constituent spouse attributes are used heavily in RE and are relied upon by our fundraisers who must be able to see these in NXT. Now we must face the decision whether to undertake a big project by moving the spouse attributes onto the constituent attributes, which is not desirable. We shouldn't be forced to find workarounds for NXT and use fields in matters for which they are not intended.
Would be great to see some movement on this!!!
Is there an update on this? It is so important to see thes constituent relationship attributes for our organization contacts.
Attributes hold a lot of great information about a record. Please make them visable in NXT
I agree - relationship attributes are very important, particularly those for organisation contacts which are used for a number of purposes, including filtering in queries, exports and mail.
Educational Attributes are a MUST-see in NXT!
Please make this viewable in NXT. We store a lot of information in attributes for spouses and children who should not be full records. So frustrating not to be able to see this in the web view.
This is very much needed - we need custom fields for non-constituent relationships.
Agree! Those in my org who are more out and about in their roles meeting with contacts mostly live in NXT
I can't believe that this does not show! Our database is primarily parents and we store all of their children's education and class year information in the attributes. I just did a massive cleanup of these records and it is invisible in NXT. PLEASE MAKE THE ATTRIBUTES & NOTES VISIBLE!!!