BAQs not showing up for user assigned to Access Scope

Hello!

We’re currently using an Access Scope connected to an API Key to access our BAQs from Power BI. We have a user set to only view the BAQs available in the Access Scope. However, I have been trying to add an additional BAQ to the Access Scope, but the new BAQ doesn’t appear to be accessible using the user’s credentials and API key (whereas the original ones are). When I check what the user can see what BAQs the user can see through the API help page, they can only see the BAQs that were originally there.

Using the debug tool it looks like the BAQ is being added correctly to AccessScopeSvc, and when I use my credentials I can access the BAQ from PowerBI. I was not the one who setup the user, so I’m not sure where I can go to check if there is something incorrect with their access.

Where can I ensure that the Access Scope is being properly updated for the user? Or what issue might be occurring?

1 Like

Is the baq shared?

It is

Check the Security ID on the BAQ; make sure it is the same as the working BAQs.

Are you using v2 API with the API key and the user/pass? In my experience I have to use both. And I always pull data using my integration user account “datapuller” that is not associated with any specific user. IDK if this is right, but it works well enough:

2 Likes

But did you actually go look at the access scope and see if the new BAQs are there? Kind of unclear.