nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Retiring database view Attributes in Jan 2026

Helen Trevain

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?

Find more posts tagged with

Accepted answers

All comments

Jill Deming

I am tiring of the step by step process of this NXT implementation. I do not have the time to check things that seem to be changing weekly. Perhaps it is because I remember when they implemented NXT and declared that "everyone" would be using NXT exclusively over the next 2-3 years. This was in 2014. 11 years later we are still struggling with full functionality in either one or the other database. This is neither cost effective or productive. I don't have the time to monitor the updates everyday and peruse the blogs and attend webinars. It's all consuming.

Kimberly Abel

Yes, these are my sentiments exactly! They should implement full functionality in NXT and then start shutting down areas in database view.

Deb Dressely

I understand the movement of custom field management to webview. But still concerned about how this will appear in database view. For instance, attachments (also known as Media) are not available in database view if they were entered in webview. If they are entered in database view they ARE visible in both webview and database view. And lately I'm seeing unified view? Is this a new name for webview or is there another product being rolled out? I also agree we could use a better sight line and source of truth for changes. There is no clear place to go between community, customer success managers, developers, knowledgebase, for up-to-date and reliable information regarding changes. Knowledgebase shows April 2025 as the latest Product Update Briefing? What's Recent? What's New? none of these mention the migration of attributes/custom fields. Keeping up with Blackbaud could be a full time job if I didn't have other tasks and responsibilities.

Elizabeth Johnson

https://community.blackbaud.com/discussion/comment/307416#Comment_307416

I want to bring Crystal's sharing of Trit's recent blog back to the bottom of this thread. I think Trit is selling herself short with her time and expertise at BB - Her name is familiar going way back. Thanks to @Aldera Chisholm, @Alex Wong, and @Austen Brown for sharing more insight. This feels very manageable for my organization that has been using RE since 1987. @Deborah Drucker I hope this helps.

Jonathan Angell

@Alex Wong

So it seems the Customer Success team use an "internal AI-powered knowledge tool, which pulls together official insights from various internal teams to provide detailed guidance". This is a recipe for confusion, to say the least - as it means users are receiving "confirmation directly from Blackbaud employees" which are in contradiction to each other.

I challenged the Customer Success team because their answers are clearly AI generated, and also factually incorrect. This is a serious issue that Blackbaud should be addressing - they cannot simply place untrained members of staff in a role to rely on an AI system which appears flaky at best.

Full transcript of their third confirmation of their view that database and web view links will be severed (which, for the avoidance of any doubt, is wrong!)

………………………………………………….The information below is factually incorrect!…………………………………..

Hi Jon,

Thank you for your thoughtful follow-up and for referencing the blog post by Trit Mulligan. I appreciate the opportunity to clarify the current and upcoming behavior regarding Custom Fields and Attributes in Raiser’s Edge NXT.

You're absolutely right that, as of today, when a Custom Field is created in web view and added to a constituent record, it appears in the database view under the Attributes tab. However, this behavior is part of the current transitional state and will change starting January 2026.

🔄 Sync Behavior – Now vs. Post-January 2026

Action	Current Behavior	Behavior After January 2026
Add existing Custom Field to a record in web view	Appears in database view under Attributes tab	Will NOT appear in database view
Add Attribute to a record in database view (via import or direct edit)	Does NOT appear in web view	Still will NOT appear in web view

To directly answer your question:

If we create a new Custom Field in web view, and add it to a constituent record, will we be able to see that Custom Field in database view on the constituent’s record’s Attribute tab?

After January 2026, the answer is no. Custom Fields and Attributes will be managed independently. Custom Fields added in web view will not sync to the Attributes tab in database view.

🧭 Why This Change?

This shift is part of Blackbaud’s broader strategy to unify configuration and data management within the web view. Just like Code Tables, Attribute management is moving entirely to web view. While existing Attributes will remain visible and usable in database view, all new configuration including Custom Fields must be done in web view going forward.

✅ What Will Still Work in Database View?

You can view and use existing Attributes on constituent records.
You can import and globally add existing Attributes via tools like Import or Global Add.
You cannot create or modify Attribute types in database view after January 2026.

📌 Summary

Custom Fields created in web view will not appear in database view after January 2026.
Attributes added in database view will not appear in web view.
Export and Queue functionalities are on track to be fully transitioned to web view by January 2026.

We understand how important this is for your reporting and workflows, and we’re here to support you through this transition. Please don’t hesitate to reach out with further questions or let me know if you wish to discuss about this in detail with our Customer Support Team - I'll be happy to raise a ticket on your behalf.

Alex Wong

@Jonathan Angell that's terrible. I am at BBCON this week, and already told the AI team about this, and there will be a session on Support, which I will bring up as well.

Suzie Capps

https://community.blackbaud.com/discussion/comment/307584#Comment_307584

Massively appreciate you doing this! I do feel like some noise needs to be raised whilst the "big-wigs" are in the building - the only chance to do so. Please spread the word around the conference and if possible get as many people together to raise this as an issue.

Faith Murray

Despite the announcement, it does seem as if this particular transition is confusing not only to users, but also to Blackbaud staff at this point.

Deborah, if the Custom Fields/Attributes exist in webview, then you should be able to use webview query to pull a group of constituents. Once that group has been created in a static query, the system creates record keys for the constituents that persist irrespective of any other record fields such as attributes, which can be edited after a static query is grouped without affecting the query output. So linking an Export in database view to that webview query will still pull your intended audience.

I think the main point I get out of this thread is that we need to make sure we communicate to BB which functionalities we need to have working at the time attributes switch over. I'm sure they will adjust their schedule as necessary to make sure we have the functionalities we need for day-to-day work. I haven't ever seen them leave us unable to perform critical operations. There's always a solution to management (even if it does occasionally become clunkier than before, like external letter merges) before they eliminate a feature. So our job is to communicate to our account reps, to support staff, and on the Community and Idea Bank what features will be critical for us in Attribute management before the January transition comes.