Since Tables will only be accessible via webview and no longer by database view from October 2023, please make code table reports available (as a spreadsheet export if possible) in webview.
This is particularly useful for maintaining the active and inactive entries for tables that we use with attributes/custom fields as some have a large number of entries and users who will not have access to edit tables themselves play a big role in this maintenance. Typically, we export the table entries, share them with users and they highlight those that should now be inactive before returning the list for administrators to tidy.
If this is "planned", can it be added as a line item to the Feature Grid so we can know when to expect it? Right now it says Basic Table Management is Available in web view, but without the ability to export tables for review and clean up in a spreadsheet format, basic management is not available.
Agree. We definitely need the ability to export table values in Excel. This is a basic tool and should be available.
Adding my two cents in hopes this functionality will be added back. Appreciate that you all are trying to make a unified view but when functionality is lost its not a good thing.
When will we be able to export tables from web view? This is a basic functionality that was lost when this was moved. We need it back asap.
It is extremely difficult to work in tables without a report or export functionality - including number of uses. I have lost hours of work using workarounds for a feature that was included in the database view.
Please add this sooner rather than later!
Via "Sunshine Reinken", this idea is marked as "Planned". Does this mean that Blackbaud WILL HAVE the functionality to print / export tables? Or is this still in the "Idea Bank", which means Blackbaud may still not have this functionality?
When is this happening? This is incredibly annoying not to be able to export tables!!
This idea is marked as "Planned" with no comment or update from Blackbaud staff to determine what the time frame is.
Why was this not an export function brought over at the same time as tables? Again, forcing us to use both views to accomplish our jobs.
I am having less and less confidence in the statements made by Blackbaud that "web view will have all the functions / features that are in database view."
Everything everyone said above.
I am currently trying to bring in matriculation schools for alum, which in itself is a time-consuming task of checking for existing education records, and later this Spring will be bringing in high school/college education records for new parents, a similar process. We try to avoid creation of duplicate school name entries in the Schools table because it is already very lengthy without duplicates. So, we like to first identify which school names can be found in RE and do a clean-up process in the spreadsheet work before we move to the import process/troubleshooting exceptions there (school name may not be the only exception that needs resolving; we don't like to use import as our first point of identifying school names not found). Copying and pasting a very large Schools list from the RE NXT web page to Excel sometimes fails (waiting on browser to respond to copy/paste) and requires multiple steps to get to a final, clean list when it does work. Not being able to export the full list of existing table entries for the Schools table is very discouraging and adds to an already lengthy number of steps. It is hard to understand why functionality that seems pretty basic was not added before it was disabled in database view. The AI response to a search on "export table" is pointing me to article 114551, which doesn't seem to apply/work for this scenario.
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...