Forum Discussion
Error in Power BI reports which are build using Direct Query
Hello Anonymous ,
I have build 3 power bi reports using one dataset. Firstly I built a dataset(semantic model), then I built the other 3 reports using this semantic model as the source through direct query. Even though I have admin access to the Workspace I'm getting the following error .
Any gudidance on this are highly appreciated!
Regards,
Kishor
Hii Ramkishor
To Fix It
Step 1: Grant "Build" Permissions on the Semantic Model
Admin access allows you to manage the workspace, but the DirectQuery connection specifically requires Build permissions to query the data from a different report file.
- Go to the workspace where the Semantic Model (Dataset) is located.
- Click the three dots (...) next to the model and select Manage Permissions.
- Go to the Direct Reports tab.
- Ensure your name (and the names of the report viewers) has Read and Build permissions. If "Build" is missing, click Add User and check the box for "Allow recipients to build content with the data associated with this semantic model."
Step 2: Update Data Source Credentials in the Service
If the reports were moved or the model was republished, the credentials for the DirectQuery connection might have been invalidated.
- Go to the Settings of the Report (not the model).
- Look for Data Source Credentials.
- If there is an error message or a "Sign in" prompt, click Edit Credentials.
- Set the Authentication Method to OAuth2 and the Privacy Level to Organizational.
Step 3: Check "Discoverability" (If in different Workspaces)
If your reports are in Workspace A and the semantic model is in Workspace B:
- Go to the Semantic Model settings in Workspace B.
- Ensure "Discoverability" is enabled if you are using a Pro or Premium Per User license.
- Ensure the "Allow users to query datasets with a Live Connection" setting is enabled in the Admin Tenant Settings.
Summary for the Community
Being a Workspace Admin is often not enough for cross-report DirectQuery connections. You must explicitly ensure Build Permissions are granted on the source semantic model and that OAuth2 credentials are refreshed in the report settings.
If granting Build permissions restores your report visuals, please mark this as the "Accepted Solution"!
8 Replies
Hi Ramkishor
can you clarify what you mean by direct query?
Did you mean live connection ?
Or did you mean a modified live connection that becomes a directquery to AnalysisServices?
If this helped, please consider giving kudos and mark as a solution
@me in replies or I'll lose your thread
Want to check your DAX skills? Answer my biweekly DAX challenges on the kubisco Linkedin page
Consider voting this Power BI idea
Francesco Bergamaschi
MBA, M.Eng, M.Econ, Professor of BI
Hii Ramkishor
To Fix It
Step 1: Grant "Build" Permissions on the Semantic Model
Admin access allows you to manage the workspace, but the DirectQuery connection specifically requires Build permissions to query the data from a different report file.
- Go to the workspace where the Semantic Model (Dataset) is located.
- Click the three dots (...) next to the model and select Manage Permissions.
- Go to the Direct Reports tab.
- Ensure your name (and the names of the report viewers) has Read and Build permissions. If "Build" is missing, click Add User and check the box for "Allow recipients to build content with the data associated with this semantic model."
Step 2: Update Data Source Credentials in the Service
If the reports were moved or the model was republished, the credentials for the DirectQuery connection might have been invalidated.
- Go to the Settings of the Report (not the model).
- Look for Data Source Credentials.
- If there is an error message or a "Sign in" prompt, click Edit Credentials.
- Set the Authentication Method to OAuth2 and the Privacy Level to Organizational.
Step 3: Check "Discoverability" (If in different Workspaces)
If your reports are in Workspace A and the semantic model is in Workspace B:
- Go to the Semantic Model settings in Workspace B.
- Ensure "Discoverability" is enabled if you are using a Pro or Premium Per User license.
- Ensure the "Allow users to query datasets with a Live Connection" setting is enabled in the Admin Tenant Settings.
Summary for the Community
Being a Workspace Admin is often not enough for cross-report DirectQuery connections. You must explicitly ensure Build Permissions are granted on the source semantic model and that OAuth2 credentials are refreshed in the report settings.
If granting Build permissions restores your report visuals, please mark this as the "Accepted Solution"!
Hi AshokKunwar. Thanks for the above, really useful. But do you know why there is a need to give Build Permissions to the viewers? We have this same problem, where report author connects to a data set in another workspace, and then uses that data with other data sources to create an aggregated view in another workspace. The report is set up using DirectQuery and it used to work, so something has changed somewhere. The report author is not the owner of the data set in another workspace, but she has build permissions on it. Would she also need Share permissions, in order for her report viewers in her workspace to be able to see the aggregated report elements? Thank you in advance.
You need to have Build access to that semantic model.
Hi Ramkishor,
Thank you FBergamaschi AshokKunwar lbendlin, for your insights.
This error can happen if a report uses a Power BI service live connection to a shared semantic model, as Build permission is required. Workspace Admin rights alone are not sufficient; without Build permission, live queries fail with “Cannot connect to the data source.” To resolve this, grant Build permission on the semantic model via Manage permissions, then refresh the report.
Connect to semantic models in Power BI - Power BI | Microsoft Learn
Semantic model permissions - Power BI | Microsoft Learn
Build Permission for Shared Semantic Models - Power BI | Microsoft Learn
Thank you.
Hii Ramkishor
If granting Build permissions restores your report visuals, please mark this as the "Accepted Solution"!
Hi Ramkishor,
Have you had a chance to review the solution we shared earlier? If the issue persists, feel free to reply so we can help further.
Thank you.
Hi Ramkishor,
Checking in to see if your issue has been resolved. let us know if you still need any assistance.
Thank you.
