I last commented on this thread in March 2023. The gift aid declarations have now made an appearance in NXT but the Tributes and flexible JG integration are still missing. I am hoping at BBCon next week they may have an answer to when things will happen. I'm not holding my breath though, it seems that anything required in the UK is not being looked at.
For this to get to almost 800 votes shows how important it is to NOT do away with the database view until everything is available through the web view. Also as to why webview should NOT be touted as the greatest thing when you cannot pull a simple list for mailing... which is not only very common, but every single organization completes this task, yet it is not adequate to use webview to complete this task. As it is today an example of how inadequate the webview is - a year ago (August 2023) someone made a request/suggestion to be able to pull addressee & Salutation (including additional custom ones) in list view - but here it is a year later, and that is still something that is unavailable in webview with lists. This issue is actually quite crucial to most orgs who have multiple teams/leaders pull lists, but they cannot use them for mailings. Just want to be crystal clear - please make this happen soon.
This is the first I have heard that database view is scheduled to end soon and I hope it is just a rumor. There is NO way I can do my job using the functions available in the NXT web-view. My biggest fear is that Blackbaud will add query, export, import, and reporting functions to the web-view that are not fully functional and don't mirror the exact features available in database view.
I too have to ask why Blackbaud feels it is necessary to end database view? What is the harm in keeping it for those of us who need to access all of the functions I mentioned? In our office, the fundraisers love to use the webview and the ops team loves the database view. So why not keep both and keep all of your clients happy?
Like many others have mentioned, I also work almost exclusively in the Database view. There are too many important functions in the database view that if they are not fully functional in NXT, will be useless. I have also had the issue of having to duplicate a lot of my work in NXT, when it is clean and precise in the database.
I mainly work with gifts & batches in RE - database view for sure has much more functionality at present. In particular we need to have something that notifies us when a constituent address has changed as a result of information they've submitted & a "global change" feature just in case an donate or event form has been set up incorrectly.
NXT is NOT ready for Database to be turned off. I only work in Database view and will continue to do so until everything including Query, Export, Reports, Mail, Batch, Admin, Config functions are present and working in NXT.
Has Blackbaud ever given a reason WHY database view needs to go away? We have decades of infrastructure built in DB, we work well in it, and honestly webview makes a product like Salesforce look more than equivalent if we have to rebuild everything anyway.
I wholeheartedly agree, if all the functions for a DBA are not available in NXT what is the point of using NXT? I have been working in Raiser’s Edge since 2003 and we have been hosted since October 2019. As the DBA, I very rarely go into NXT since all of my work can be accomplished easily and precisely in the database view. When I have extra time, which is never, I try and create and duplicate things in NXT, only to be frustrated. Please do NOT turn off Database View for all of us who need it to complete our work.
We're wasting too much time trying to get NXT to work for the task-at-hand, only to have to duplicate the work by going back to Database View to preform the relevant work.
I ran into the issue today of NXT appeal reporting lagging WAY behind the database reporting. Trying to keep tabs on where we are with Giving Tuesday in real-time is not possible in NXT! Yikes.
It is imperative that all NXT functionality be available in the database view whilst the database view is the only place to do imports etc. Otherwise you have to go into NXT and manually add data after the import, which defeats the purpose of the import function. Example, solicit code dates in NXT but not DB view and not available to import through a solicit code import.
I extensively use database view for RE Imports, Global add, Global changes, Exports, Queries including merging queries, linking database fields from back to Power BI etc. So we do not want DB view to be removed .
It would be really helpful if Pledges could be added in webview as well as in database view. I didn't realise this wasn't an option, recorded a gift in webview which I then wasn't able to edit either in webview or database view and the gift is now inaccurate. Please implement this function into the next update.
There is no way in **** BB can switch off Database View until the Query functionality in Database View is replicated i*n its entirety* in Web View. Sorry, but "Lists" just doesn't cut it.
We need all the separate fields available in Lists as columns and filters (including complex filters). Perhaps we need a Superuser or Admin User List area that has the full set of fields and an advanced query tool.
One of my biggest issues with web view is soft credits. We have donations that come through third party orgs. While in the listing I can see what amount is credited to Company A for individual donations, the totals are based on the full soft credit amount. This includes when I download spreadsheets to get the summary of donations for the year or all time. In web view, I can get the accurate summary and reports without this issue.
BUMP. Using NXT for the first time in my nonprofit career, and as an experienced software and tech manager, it is appalling that Blackbaud released NXT while it still lacks sooooooooooo many of the features of the database view. Insanely frustrating.
I last commented on this thread in March 2023. The gift aid declarations have now made an appearance in NXT but the Tributes and flexible JG integration are still missing. I am hoping at BBCon next week they may have an answer to when things will happen. I'm not holding my breath though, it seems that anything required in the UK is not being looked at.
For this to get to almost 800 votes shows how important it is to NOT do away with the database view until everything is available through the web view. Also as to why webview should NOT be touted as the greatest thing when you cannot pull a simple list for mailing... which is not only very common, but every single organization completes this task, yet it is not adequate to use webview to complete this task.
As it is today an example of how inadequate the webview is - a year ago (August 2023) someone made a request/suggestion to be able to pull addressee & Salutation (including additional custom ones) in list view - but here it is a year later, and that is still something that is unavailable in webview with lists. This issue is actually quite crucial to most orgs who have multiple teams/leaders pull lists, but they cannot use them for mailings.
Just want to be crystal clear - please make this happen soon.
This is the first I have heard that database view is scheduled to end soon and I hope it is just a rumor. There is NO way I can do my job using the functions available in the NXT web-view. My biggest fear is that Blackbaud will add query, export, import, and reporting functions to the web-view that are not fully functional and don't mirror the exact features available in database view.
I too have to ask why Blackbaud feels it is necessary to end database view? What is the harm in keeping it for those of us who need to access all of the functions I mentioned? In our office, the fundraisers love to use the webview and the ops team loves the database view. So why not keep both and keep all of your clients happy?
Like many others have mentioned, I also work almost exclusively in the Database view. There are too many important functions in the database view that if they are not fully functional in NXT, will be useless. I have also had the issue of having to duplicate a lot of my work in NXT, when it is clean and precise in the database.
I mainly work with gifts & batches in RE - database view for sure has much more functionality at present. In particular we need to have something that notifies us when a constituent address has changed as a result of information they've submitted & a "global change" feature just in case an donate or event form has been set up incorrectly.
NXT is NOT ready for Database to be turned off. I only work in Database view and will continue to do so until everything including Query, Export, Reports, Mail, Batch, Admin, Config functions are present and working in NXT.
Has Blackbaud ever given a reason WHY database view needs to go away? We have decades of infrastructure built in DB, we work well in it, and honestly webview makes a product like Salesforce look more than equivalent if we have to rebuild everything anyway.
I have not heard about a "switch off." The functionality is far from ready to do that.
Switching off Database View is the worst idea in the history of ideas. Please don't.
I agree with the comments posted. We keep saying use NXT but the functionality even for events sends you back to database view.
I wholeheartedly agree, if all the functions for a DBA are not available in NXT what is the point of using NXT? I have been working in Raiser’s Edge since 2003 and we have been hosted since October 2019. As the DBA, I very rarely go into NXT since all of my work can be accomplished easily and precisely in the database view. When I have extra time, which is never, I try and create and duplicate things in NXT, only to be frustrated. Please do NOT turn off Database View for all of us who need it to complete our work.
We're wasting too much time trying to get NXT to work for the task-at-hand, only to have to duplicate the work by going back to Database View to preform the relevant work.
I ran into the issue today of NXT appeal reporting lagging WAY behind the database reporting. Trying to keep tabs on where we are with Giving Tuesday in real-time is not possible in NXT! Yikes.
It is imperative that all NXT functionality be available in the database view whilst the database view is the only place to do imports etc. Otherwise you have to go into NXT and manually add data after the import, which defeats the purpose of the import function. Example, solicit code dates in NXT but not DB view and not available to import through a solicit code import.
I extensively use database view for RE Imports, Global add, Global changes, Exports, Queries including merging queries, linking database fields from back to Power BI etc. So we do not want DB view to be removed .
It would be really helpful if Pledges could be added in webview as well as in database view. I didn't realise this wasn't an option, recorded a gift in webview which I then wasn't able to edit either in webview or database view and the gift is now inaccurate. Please implement this function into the next update.
There is no way in **** BB can switch off Database View until the Query functionality in Database View is replicated i*n its entirety* in Web View. Sorry, but "Lists" just doesn't cut it.
We need all the separate fields available in Lists as columns and filters (including complex filters). Perhaps we need a Superuser or Admin User List area that has the full set of fields and an advanced query tool.
One of my biggest issues with web view is soft credits. We have donations that come through third party orgs. While in the listing I can see what amount is credited to Company A for individual donations, the totals are based on the full soft credit amount. This includes when I download spreadsheets to get the summary of donations for the year or all time. In web view, I can get the accurate summary and reports without this issue.
BUMP. Using NXT for the first time in my nonprofit career, and as an experienced software and tech manager, it is appalling that Blackbaud released NXT while it still lacks sooooooooooo many of the features of the database view. Insanely frustrating.