Retiring database view Attributes in Jan 2026

Helen Trevain · September 26

Hi everyone. Blackbaud announced this week that they will begin to retire some functionality from database view (notably functionality that isn’t used widely on a daily basis). For example, database view attributes will be retired, and custom fields will become exclusively available in web view in January 2026. We use database view Attributes for all our consents and preferences so they are used heavily on a daily basis. Is anyone else shocked about this announcement and have massive concerns around the lack of notice period?

JoAnn Strommen · September 26

I understand your concern. We use attributes significantly as well.

In addition to the 'retirement' I am disappointed that there is still no global add function to add the attrbitutes in web view. As we record campus activities/groups that alum were involved with on campus as well as special mailings and contact preferences, it's always a challenge to look at a record in "unified view" and only be able to see 5 entries without additional clicking. IMO, not user friendly.

Again, nice for development officers, not for data folks.

Dan Snyder · September 26

For me, I think the biggest thing is the ability for global adds. Hopefully someone from BB can clarify this, but I suspect you can still globally add and import attributes/custom fields (why two names?!?! I digress).

I say this because global adds are their own process area. Also, while tables are only managed in webview/unified view, in an import you can still select to add new table entries so I presume the functionality of importing attributes/custom fields will remain. If you need to add a totally new attribute/custom field that would have to be done in webview/unified view but then you could use import as normal.

@JoAnn Strommen I do get the only seeing 5 at a time and I have gotten a bit better at using the filter on the tile, but still not great for us data lovers who want to see it all at once!

Joe Moretti · September 26

Is anyone else shocked about this announcement and have massive concerns around the lack of notice period?

Unfortunately no, because this whole RE NXT or Unified View has been a complete SHITSHOW thanks to Blackbaud and this horrible process. They really do not even take their customers concern that serious and do whatever they want. Just shoving this RE NXT down our throats and not making sure everything done in database view can be done in RE NXT like Action Tracks!!! This company has gotten greedier every year, while their product and customer service go down!

What about:

Action Tracks being in RE NXT (and no, workflow is NOT the same thing),

The plugins Section

Deceased Finder (not the inferior one in RE NXT that automatically marks everyone deceased when you run it)

RE MAIL (especially quick letters and the segment feature)

Action Reminders……………………………….. and this is just a few things.

So more of let's dumbdown RE NXT as opposed to making RE Database View better. Ever try working with their Insights, AWFUL AWFUL AWFUL.

Veronica Renzo · September 26

I use attributes everyday as well so I am not sure who at Blackbaud thinks it is a functionality that isn’t used widely on a daily basis. And my team uses them too. I just got over the removal of tribute linking while adding a gift. This transition continues to be challenging in everyday data management. I suggest voting on Cindy Hall's idea for Global Functionality in the Blackbaud Raiser's Edge NXT® Ideas, she posted it on 9/25/25.

Lena Payne · September 29

https://community.blackbaud.com/discussion/83629/retiring-database-view-attributes-in-jan-2026

I agree that retiring attributes seems very rushed, but I was wondering if using solicit codes in the consent module over consents in attributes would resolve your particular issue? We transferred all our consent attributes to solicit codes and it is working well atm.

Rachel Cavalier · September 29

As Jo and Dan have mentioned, I too am bothered by only seeing 5 custom fields at a time - which has been compounded by the fact that the database we merged into our existing database a few months ago used an Event attribute to record invites, attendance, that a donation was made and save the date communications! I'm working on moving all of this to a more sensible place but in the meantime it's maddening.

Karen Diener · September 29

To be clear……

This does not mean that attributes / custom fields are going away. It just means that when you want to configure a new one, you will do it in webview instead of database view. That is all.

Dan raises the most important concern in my mind right now, which is whether or not you will be able to global add / change them, or import them. That functionality is in database view right now but won't be coming to webview for about a year if BB stays on schedule.

PLEASE read for comprehension, and think a bit before reacting. Believe me, I have many issues with how functionality is rolling out, the UI of webview, what functionality is being prioritized, customer support, clear communication, and so on and so on. But I strive to read release notes carefully and think about how the change will impact the customers I support. Very often, it is less disruptive than it appears on an initial read.

Alex Wong · September 29

@Karen Diener thanks for the context, I was going to ask what exactly is retiring as there is no link or screenshot of the said change. (please provide link to read up on this change if someone has it)

If the change is only the "config" > "attribute" section of the dbview functionality, I have no problem with it being retired as it appears to works without issue.

Anyone having trouble with using the configuration of custom fields (attribute) on the webview? let's share what might not be working so it can be identified and fixed.

Aldera Chisholm · September 29

Hey folks - lots of suggestions of features we need in this thread… when you have identified something, please link to where you've added it in the Idea Bank so the rest of us can support you and vote on them! We've seen how they do check and respond to the idea bank, so it's worth our time to support each other when there are things in there you also want to see!

Helen Trevain · September 30

Much clearer and detailed communication on all changes needs to come from Blackbaud so it is crystal clear for everyone to understand the full impact of each one. The way things are being communicated at the moment isn't good enough as it leaves things open to interpretation and causes unnecessary stress and worry.

Austen Brown · September 30

https://community.blackbaud.com/discussion/comment/307345#Comment_307345

Absolutely this! @Karen Diener thank you for breaking this down and formatting it for readability. This conclusion was confirmed in another chat in the FB Group, when another user shared a conversation with chat support that what's moving is only Custom Field/Attribute Management - custom fields/attributes on records will still be visible in both views.

I know announcements like this can feel like a challenge, change is especially tough as we approach year-end. While frustrating at first, not everything that’s moving is worse, some things are actually better. For example, adding a new table is now more straightforward: instead of scrolling through a never ending list to find the [Add New Table] option, you can just click the “+ New” table button. Re-ordering category lists is also easier.

If something you need is missing, add it to the Idea Bank. Blackbaud actively reviews ideas, and topics with high engagement often inspire product improvements. Recent examples include Query Lists, Query Control Reports, Fund Relationships, and Printing Report Criteria on Standard Reports - all user-driven ideas now marked as planned or shipped.

Jonathan Angell · September 30

Support confirmed to me that, after January 2026, if a new Custom Attribute is created in web view it will not appear in database view for use. So this is more than just stopping the creation of Attributes in database view!

"From January 2026 onwards, creating a Custom Field in web view will no longer result in a corresponding Attribute appearing in database view. Custom Fields and Attributes will be managed independently, and any new configuration, such as adding a new consent type or preference, will need to be done directly in web view."

Alex Wong · September 30

@Crystal Bruce I think it is important that someone from Blackbaud is confirming this. We are getting a lot of "from Blackbaud". But I have not seen the actual post from Blackbaud and when speaking with support, there are many chance of miscommunication.

@Jonathan Angell it is highly unlikely that custom field (which is exactly the same as attribute, just named differently on webview vs dbview) that is configured in webview is not available in dbview to use

Darlene LeVielle · September 30

With the transition to the Web View, can it be clarified whether bulk updates to custom variables/attributes will still be supported in January 2026 at the time feature is turned off in DBV? For example, if values need to be applied to 600~ records, will this require manual entry through the web interface, or will there be a bulk load option available in January 2026? If bulk updates to custom variables/attributes are not supported in the web view starting in January 2026, what approaches can be used to update a large volume of records? Are there BB specific recommended workflows or workarounds for handling this scenario efficiently until feature is deployed?

Would anyone be able to share when this feature in WBV is expected to go Live? Is there a published development roadmap we can reference, prior to registering for a 'What’s New' or recent updates session on this specific functionality?

Thank you for any guidance on this.

Alex Wong · September 30

@Darlene LeVielle what you are asking is "Import" and "Global Add" function of the dbview, which is not what is being discussed here. There is no communication from Blackbaud that "Import", "Global Chnage", and "Global Add" is going away yet as these functionality does not exist in webview yet.

Darlene LeVielle · September 30

Thank you for this information. Let me restate to be sure I understand. My question is specifically about how we will populate this field in bulk once Database View access is retired in January 2026. If Global Add, Import, and Global Change are not available in Web View, what options will exist to update these fields across hundreds of records at once? Is there guidance on the planned approach?

Alex Wong · September 30

DB view access is NOT retiring on Jan 2026

Darlene LeVielle · September 30

If database view access is retired for this field specically, as I noted here above.

Thank you all for any additional insight.

Crystal Bruce · September 30

Hi! This blog was recently posted in Raiser's Edge NXT

Blackbaud Raiser’s Edge NXT® Query: Shaping the Future Together

It included this comment from Trit Mulligan from the Product team. I hope this helps!

Hello!
I’m Trit Mulligan, and I recently joined the Product team for Raiser's Edge NXT. While I’m new to this team, I’ve been with Blackbaud for some time—most recently working to bring new donation forms to Raiser's Edge NXT through Online Giving.
First and foremost, I want to make sure you didn’t miss the key point: queries will remain available in database view based on your feedback.
What is changing is how attributes are managed. Similar to code tables, attribute management is moving to web view. But rest assured, all existing functionality will still work in database view, including globally updating.
We’ve updated our original post to make this clearer, and we appreciate your feedback in helping us improve that message.
Our goal is a unified experience in web view, but until we fully transition, you’ll continue to see references to both web view and database view.
And most importantly—we want to hear from you. Your feedback helps shape the future of Raiser's Edge NXT, so please keep sharing your ideas and insights!
I’m looking forward to seeing many of you at bbcon! It’s always a great opportunity to connect, share ideas, and hear directly from you.
Also, keep an eye out for details on our upcoming Product Update Briefing, scheduled for mid-November. We’ll be sharing important updates and insights into what’s ahead for Raiser's Edge NXT.

Alex Wong · September 30

Thank you Crystal for posting.

As web view becomes more robust, we will move some capabilities exclusively into web view. For example,
management
of Attributes under Configuration in database view—including creating, editing, and deleting—will move exclusively to Settings, Custom fields in web view in January 2026.

So as Karen stated, it is only Configuration > Attributes that will be removed from dbview. And my experience with webview attribute (custom field) configuration has been positive. So I have no problem this functionality being removed from dbview.

Jonathan Angell · October 1

https://community.blackbaud.com/discussion/comment/307390#Comment_307390

Yes, I was surprised by Blackbaud's answer. The implication from the customer support agent was that the link was to be severed, so that a newly created custom field would not be available to use as an attribute. But I agree that that is not how BB have been migrating things to date, so it may be a miscommunication - however this was an answer given to me after I asked a clarifying question, because I couldn't believe the first answer that I was given (that new custom fields would be unavailable to use).

I suspect it may be that the pace of progress is not being well communicated within Blackbaud, so only the developers really know what the truth is, and all the support staff are as clueless as us :(

Jonathan Angell · October 1

@Alex Wong I asked more clarification questions. This is rather worrying!

1. After January 2026, if we add a custom field to a record in web view, will it still appear in database view under the attributes tab?

No, it will not. Starting January 2026, custom fields will be exclusively available in web view, and attributes will be retired from database view. This means that even if you're adding an existing custom field to a record via web view, it will not reflect in the database view under the attributes tab.

2. After January 2026, if we add an attribute to a record from database view (via import or direct edit), will it display in Custom Fields when viewing the record in web view?

No, it will not. Since attributes are being retired from database view in January 2026, any additions made via database view (including imports or direct edits) will not sync or display in the web view's Custom Fields section. All future additions and edits to custom fields must be done in web view.

3. Will Export and Queue be fully transitioned and functioning in web view by January 2026?

Yes, both Export and Queue functionalities are scheduled to be fully available in web view by January 2026. The roadmap confirms that these features are part of the Q4 2025 and Q1 2026 rollout, with enhancements to structured templates and queue management already in progress.

Alex Wong · October 1

@Erik Leaver @Crystal Bruce what Jonathan Angell posted is concerning and this post is getting rather out of hand. Crystal's post on what is upcoming is very clear to me, that what is being retired Jan26 is ONLY the configuration of the attribute (in true technical terminology, meaning the creation of new attribute category), not the creation and usage of attribute itself.

@Jonathan Angell please post your Blackbaud support case number here, Erik and Crystal will be able to make sure whoever you were speaking to, were corrected for spreading misinformation.

Erik Leaver · October 1

@Alex Wong This is very much a question for the RENXT team. I don't have much to contribute other than when I look at the case transcript, here's what the analyst provided:

"From my knowledge the current circumstances are the data will still exist e.g. Custom fields is just Web View terminology for Attributes, so they can still be managed in the Web View being known as Custom Fields, it's the management of Attributes in Database View that will be retired.

Right now, Support doesn't have any information to share at this time that delves into this further. This announcement was the same information shared to us and more details on this will come as the roadmap is progressed further, so my suggestion will be to keep an eye out for Product Update Briefings for RE NXT since these are covered via these: https://www.blackbaud.com/product-update-briefings "

This seems accurate. If there were other statements made, I don't see them in the chat. If follow up is needed, contacting the account team is the best course of action to escalate.

Jonathan Angell · October 3

@Alex Wong This was not a support case, as Support seem to have as little unformation as us and our fellow users have. This was a response from the Customer Success team (two different agents) from EMEAcustomersuccess@blackbaud.co.uk

I'll post Trit's blog comment back to the agents who were dealing with me, to see that they say. No need for you to take any action, though thank you for the offer.

Cathy Winning · October 3

I'm very disappointed. We lean heavily on attributes to track so much. I hope they change their minds on this.

Mark Guncheon · October 3

We are in multiple markets and one of the ways we use attributes is to use a unique attribute for each market. We also code board members with attributes. I actually saw this coming back when we started using NXT and realized that as with other names, BB decided to use the term custom field rather than attribute. I had hopes they would eventually correct this but that was not to be.

Aldera Chisholm · October 3

https://community.blackbaud.com/discussion/comment/307509#Comment_307509

They aren't going away! They are moving the management of attributes/custom fields to NXT, just as we've already seen the management of Tables move to NXT.

Alex Wong · October 3

@Aldera Chisholm It's almost funny how "rumors" spread. Even with confirmation directly from Blackbaud employee doesn't resolve.

@Jonathan Angell Yes, make sure you show your customer success team the reply from Erik Leaver.

Deborah Drucker · October 3

Does the "retirement" of Attributes from Database view mean that we will not be able to Query on them for the purposes of exporting? We just set up a whole bunch of Action Attributes, it is going to be a problem if we cannot use them.

I'm also wondering at what point we will be able to view/use Education Attributes. We have a great deal of information in Education Attributes, such as fellowship and scholarship information, which we cannot view or use in NXT.

I cannot believe how awful RE has gotten. Less and less usable.

Retiring database view Attributes in Jan 2026

Answers

Categories