Updates to Query API

Alyssa Maslankowski

We’ve made the following updates: 

• To return the number of rows found by a query, we added the row_count property to GET Query execution job. For regular query jobs, this returns the number of rows in the file. For static queries, this returns the number of keys.
• We changed the default value for ux_mode to “Asynchronous” for POST Query execution job (Ad-hoc), POST Query execution job (by ID), and POST Refresh static query execution job. Previously, the default value was “Synchronous.”
• GET Query now returns an error if the query is not currently supported in web view. You can use the view_supported property returned by GET Query list to view supported queries.
• POST Query execution job (Ad-hoc) and POST Query execution job (by ID) now support queries that suppress duplicate rows or contain no output columns. Previously, these queries returned an error.

Update to query export permissions



Tip: Don't see Query? Expect its wider release in a future update.

For Query in Raiser’s Edge NXT, we’ve introduced the Export permission under Query tasks for the Analysis role. For Query, this permission grants access to users to export query results from the query list and the query editor. For the Query API, this grants access to POST Query execution job (Ad-hoc), POST Query execution job (by ID), and GET Query execution job status as those endpoints provide consumers with files of query results.

Note: If you were previously a solution admin, the new permission is automatically assigned for you.

To create the role and assign permission to users, in Raiser’s Edge NXT, navigate to Control Panel, Security to access Security roles and User Management. For more information, see Query resources.