@David Springer - Yes please! I finally tried web queries. I exported the results of the same query in both web view and database view. Very good matchup EXCEPT that the name, which we have always used First M. Last. In web is comes out Last, First. In order to accommodate this lack of choice, I will need to do manipulations / concatenations / etc. This should not be necessary. Please allow us to choose the name format. Please.

@David Springer - Why could there not be 2 options for the name field? One that's Name (First M. Last) and one that's Name (Last, First M.)?

Changes like these are important for us to know, not just run into as we're trying to do our jobs.

@David Springer - just chiming in to confirm that yes, we would like a similar setting in webview to what we have in database view for the output for the Name field in query. I came to look for this idea today because I'm running our annual donor lists and our process uses both the standard report and a query generated from the standard report. We need the Name format in query to match my current database view settings for First Name Middle Initial Last Name. This is the format for the report and has been for over a decade. I cannot start producing a report that has Last Name, First Name Middle Initial. It will not match our past reports and will screw up our donor wall. Because this is only a once a year process, I hadn't thought about this use case, but it's really important to us.

Without the ability to control the Name format output, I will have to do some pretty complex excel manipulation to get the format I need and this will add a great deal of time to an already time consuming process. Please allow us the same flexibility we depend on in database view.

@David Springer - Chiming in with everyone too! Ours is just First Name Last Name in database view and being able to have web view match will be super useful.

@David Springer Seconding everyone on this! I'm trying to use NXT for more weekly queries and reports and this is making my tribute report difficult. The Honor/Memorial Name field is exporting everyone with Last Name, First Name which means I have to go through and fix all of them in order for the Honor/Memorial name to show up correctly when I do my Word Merge to print the cards that I mail weekly.

@David Springer That'd would be perfect for us too!

Yes, please, for the same setting as in DB to allow the individual user to determine the output of the Name. Everyone uses that field differently, and the setting allows for that.

@David Springer, yes, I want the ability to have the "name" format for a query in NXT to follow the same format as "name" produces in database view. John B Smith vs Smith, John B - which doesn't read as well in a report for colleagues. Choosing the field Name should deliver the same results in either application view.

Thanks for the idea and the comments! To clarify for anyone reading this idea, database view has a user option to determine the name format. For web view Query, we used the value that most users had in that setting. I'm interpreting this idea to mean you'd want a similar user option for web view. If that's not the intent, please let me know.

Not using NXT query until I can get the data I want in the same format as I can choose from database view. If it isn't broke, don't break it!

This is far from the only issue with inconsitencies between NXT and webview, but it's one of the annoying ones. Luckily we don't use BB exports natively in any of our outgoing data (I dump it all into SQL and do the analysis there before we share on a web platform), but it feels terrible to have these inconsistencies.

While some changes to NXT-compatible queries are to be expected, they must be kept consistent between platforms, and loss of functionality should be zero.

Please change it back, Blackbaud! This breaks queries that work perfectly fine in database view, especially anything related to the name criteria.