Having voted and looked at the list of all the other items people have voted on, it occurs to me that:

1) I am pretty sure this is the item with the most votes (by a landslide...69 votes vs 44 for the next highest), and

2) this has been open for YEARS!

All that being the case, is there any updates on this? Seems like the last person that asked this did so a year and a half ago. An update would be great...

This is a pretty serious flaw. You have a great sky api that allows all sorts of data editing, etc, but for anyone that wants to do anything in bulk there really should be a way to either 1) make a database view dynamic query available in NXT (so you can use the NXT APIs to download lists or 2) add an API that allows access to the database view directly. I have seen some things on Lists V2, but it seems like that will require a great deal of work to pull already defined lists.

Are there any updates on this idea? It has the most votes of all non delivered ideas. Is there a reason it has not been added to the planned items? Is there any information you can give us about it? ...

Access to static queries are nice, but being able to use dynamic queries would be a big improvement. We use a lot of queries that filter based on Relationships, which is something you can't do in Lists. For a few projects we're using static lists and refreshing them manually when needed, but it would be nice to be able to use dynamic lists and avoid the busy-work.

A SQL query walks into a bar and sees two tables. He walks up to them and says 'Can I join you?

BB, please don't let this punchline go to waste.

Any updates on this front? 

As NXT can now create a list from a Static Query, there must be some functionality already created.  It would make sense to create this as an endpoint as it is the core functionality to identify a discrete set of records based on any data and connects to queries, list, reports and exports in the main database.  It would therefore be sensible to continue to use this functionality to make accessible all list and reporting options in NXT from any defined data set and go a long way to make NXT more functional for all Blackbaud customers needs.  

FYI - the Blackbaud K12 API has a way to access queries ("Advanced Lists") via a "slid" value that you can dig out of the javascript that renders when you save a list. If access to RE and FE queries is overly-complicated, how about access to RE and FE NXT worklists via a unique id that can pass the list's parameters and data already specified in the output (columns) as a response to the API call?

Here's an example of Javascript from Blackbaud's K12 solutions that you can use to access lists there (the slid=49748 returns the goodness): 

javascript:__pdL(‘52586′,’Advanced%20List:%20API%20-%20list%20example’,%20’1′,%20’~slid=49748~ml=False~sln=API%20-%20list%20example’,%20”,%20’False’,%20’0′,%20”,%20’default.aspx’)

I'm pretty sure @ Jake Spirek and @ Halley Coplin could cook this up on a plane ride.

This makes sense to have a way to get a custom set of criteria. Although query logic is pretty ugly in Database view. Currently we are exporting queries using RE:Queue and importing the flat file into a datamart. This feature would allow for an API use case to replace our use of RE:Queue.

One million percent agree! I would add that retrieving a list of queries by, say, partial name, create date, type, etc should also be supported.

For the porting of our primary integration from RE7 to RE NXT this absence is a likely deal-breaker.

Just to be clear, I'm referring a function to get a list of the available Queries, and also a function to execute a query and return its results as an XML or JSON dataset.