Forum Discussion
Troubles with Dataset ExecuteQueries In Group PowerBI API
- 2 years ago
Issue confirmed! Analysis Services connections are causing the API to fail. These connections are basically created to connect to other datasets in the same premium workspace.
Regards
lbendlin That's right. There wasn't an "scp" claim in the token.
1. But it must be noted that the same token is able to query the data using DAX from a "My Workspace" using "ExecuteQueries (Not Group) API" where the SP has "read, build" permissions on the dataset.
2. I also uploaded another semantic model, a very basic one to my dataset under the same premium workspace from where I have not been successful in querying the data, as highlighted in the question. I decided to remove "Member" permission entirely from the Workspace for my MS Entra ID Security Group "Group for PowerBI SPs" and gave direct access to my MS Entra ID Security Group on the new semantic model or the dataset with "read, build" permissions. And it worked!! with "ExecuteQueries (Not Group) API" even without "scp" claim in the token.
Now I wonder if the semantic model which I am not able to query, is the problem here... Need to investigate further.
In the meantime, I would really appreciate it if you could please elaborate on any remedies regarding the "scp" claim that could be of help here. Thanks!
lbendlin I think I found the issue!
Most of our Semantic Models has a live "Analysis Services" connection to a common Semantic Model in the same premium workspace. As per the limitations of the ExecuteQueries API, both Group and Non Group,
"Datasets that are hosted in Azure Analysis Services or that have a live connection to an on-premises Azure Analysis Services model aren't supported".
Datasets - Execute Queries - REST API (Power BI Power BI REST APIs) | Microsoft Learn
Datasets - Execute Queries In Group - REST API (Power BI Power BI REST APIs) | Microsoft Learn
Neither our dataset has a live connection to the on-prem azure analysis services model, nor any of our datasets hosted in Azure Analysis Services.
But as we all know, the underlying engine of PowerBI service workloads uses Analysis Services which is not so different from Azure Analysis Services, if I remember correctly. And maybe that's why I get "PowerBINotAuthorized" exception only for those datasets that have "Analysis Services" live connection to another dataset in the same workload.
Thoughts?
- lbendlin2 years agoSuper User
Did you give build access through the app or through the workspace? App set to auto install?
- sjt902 years agoRegular Visitor
Issue confirmed! Analysis Services connections are causing the API to fail. These connections are basically created to connect to other datasets in the same premium workspace.
Regards