Very important to have the Export feature available in NXT under Control Panel/Tables. Seems crazy to move tables to NXT and not be able to have a way to export those lists.

Code tables report no longer available in database view. Cannot manage entries one by one. Must have an export of all entries to work with. This is not efficient to type all entries to share with our team in addressing clean-up projects. So basic. How can it be overlooked?

Trying to locate the code tables report in web view today so that I can work with gift officers on a new project - They need to add prospect interests.
This project cannot be done by the gift officers in web view. I have assign the fields for them in database view, so they need to know which fields are available. Exporting a table report as a guide for them would make this project go smoother.
Karen, below provides a great list of how this could be improved. I also didn't understand why, "New Donor Table," was the default selection.
Like others have mentioned, when I run audits of these tables, this is going to be a struggle.

It is vital to be able to export table values out of RENXT. Not necessarily for table clean up (that too) but for transposing values into other platforms eg: Microsoft Forms. We want to be able to offer our constituents the same options as a drop down in these platforms, so that their responses can be imported back into RE when the need arises.

A vital function for table clean-up and maintenance. Disappointing that this is not available in web view now that there is no table access in database view.

Agreed...being able to export code tables would make clean up so much easier! Please make this happen :) TIA

I am completely disappointed (but not surprised) that code tables can no longer be printed in NXT. Not really sure what the engineers were thinking, taking the database view away before the web view was fully functional. Just another downgrade...

Agreed with a ll the comments made. Also really disappointed that the table lists cannot be exported anymore as excel spreadsheets whcih was really useful for auditing/clean up purpose. Found myself having to save the web page as a PDF :-(

I want to similarly add that I often used these code table reports for data analytics to review database usage. So losing this report will make it much more difficult to review what areas of the database need to be cleaned up and simplified.

If you want to be GREAT, Blackbaud, and not merely "adequate", here are a few suggestions that would allow your users to more efficiently manage table entries AND where they are used:

• In the list of tables, show the table name and category as currently displayed, AND add a total of how often ALL of the table entries are being used in RE
  

• When you click into a table to show the entries, the description and active / inactive flag is being shown. Display the number of instances where each specific table entry is being used.
  

• When users click "view uses" they should see a list of constituent IDs and constituent names, and allowed to save it as a List or Query in webview. You are SO close, but the system record ID is not helpful at all.
  

• Ideally, allow user to open a constituent record to see use of the table entry in context. This would be a great cleanup option for situations when a table entry is used only one time.
  

• Also allow users to filter by tables that were set up for use in Attributes / Custom Reports. It is almost there because these have no category, but you cannot filter for "category is blank"
  

• Rename the button at the top to anything BUT "New Donor Table". These are not applicable only to donors. And when you DO click the button, the screen says "Add donor category table" which is potentially confusing. There are already three "donor category tables" available.

I am not able to even find our job assignment codes in the volunteer tables displayed. This is incomplete and doesn't even translate to database view - where you can at least segment by attributes. Attributes don't have a category. You have to know the table name which isn't always obvious.

Seconding Lara Couture's comment! Please make sure ALL functionality is built out before terminating a database feature.

The timeframe for this change is way too short. Also, all functionality that is offered in DBv should be available in webview when there's a change to move to webview.