nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Coming Soon: Update to Query Export Permissions

Alyssa Maslankowski

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

For Query in Raiser’s Edge NXT, we’re introducing 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 (Preview), 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: To avoid loss of access, assign the Export permission to those who need to export queries before 5/20/2024.

If you were previously a solution admin, the new permission will automatically be 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.

Find more posts tagged with

Comments

David Zeidman

That is good to know, but is there or will there be a way of determining whether a user has the rights to export data via the API. I assume that this permission sits outside of the developer app scopes. (Or how does it tie in with that?)

Alyssa Maslankowski

Hey, David! At this time, there's not a way to determine if a user has rights to export via the API. The user at your organization who is authenticated to use the API will need to make sure they've been assigned the Export permission in Raiser's Edge NXT. If that user is a solution admin, they'll have the Export permission automatically assigned to them when this update takes place.