Allow choosing file location when exporting from Web View Queries
Currently in Database View, when exporting a Query we have the capability to choose the download location. This saves time since it is done within the workflow, rather than having to open up a separate window later once the export completes and then moving the file to where it needs to go. Some of our team members always need to file exports in particular locations.
I understand that some users will be happy with the file defaulting to Downloads, however this is actually more challenging for us and requires additional actions.
I would suggest that we make choosing the download location an optional step so that it doesn't inconvenience users happy with a Downloads folder location, but also allows users who want to choose the download location up front to be able to do so.
-
G W
- Jul 7 2025
- Reviewed: Voting Open
Related ideas
Yes, we need file locations! and also the ability to name the files as we are confirming the export, as is done in Database view.
If you try to export from a report as a .csv you are not given the option to change the name of the file, it will just match the name of the report by default. So, if you were exporting the same report multiple times using different queries as a base, each one will be given the same file name and be added to your downloads. Then there isn't a clear way to tell the documents apart unless you open each one as it's downloaded, and re-name it.
TO BLACKBAUD: I understand this is probably not going to happen in Database View ever. But as you are phasing out Database View, it would be great if you could have this feature already working in Web View sooner than later. That way it will already be there by the time Unified View is Live.
Also, we tried changing our windows default for downloads to OneDrive and RENXT files still download to the C:user\downloads folder.
Security of data should be top of mind when allowing export. We would like to set the default to be in a protected One Drive or SharePoint folder instead of the downloads folder on a PC or Laptop that can be stolen and data compromised. We have many users trying to convert to webview and this limitation is not great for data security.
I absolutely agree. With the move to a unified web-view, this feature is critical to move over to NXT across the board for any items that are exportable from the database (exports, queries, reports, etc)
Yes, very much needed! I use this feature daily in database view. This is a big part of what's holding me back from using Query in web view on a regular basis. It's so much more cumbersome to export from a query in web view.
This feature would be especially helpful if the resulting file simply needs to overwrite an old version (such as a file used for a Power BI report). It also poses a hurdle for releasing permissions to export from query since users need to actively remember to move the file to the desired location and not simply accumulate files in their downloads folder.