A DirectQuery connection is required error

[OWG25]

Good morning all,
I'm having an issue where my semantic model wont refresh due to errors in one table. I have went into the PBIX file, intending to disable load to data model for this table to fix this issue temporarily. However, when I go to view the semantic error I get a message saying that a DirectQuery connection is required, When I go to proceed I get an error (pictured)

I defintiely have access.

In addition to this, the dataflows used in this report are all refreshing correctly and are definitely connected. When i go to view data source settings inside of the report, rather than showing current connections it shows a list of dataflows present in my organisations workspace.

Is there any way to fix this without rebuilding the report? I've tried everything I could possibly think of and nothing seems to work

Thanks in advance

[v-hjannapu]

Hi @OWG25,

I would also take a moment to thank @DataNinja777  , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Regards,
Community Support Team.

[v-hjannapu]

Hi @OWG25,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We are always here to support you.


Regards,
Community Support Team.

[DataNinja777]

Hi @OWG25 ,

Based on the error messages you're seeing, the problem is almost certainly that your Power BI file is built as a Composite Model, meaning it connects to an existing semantic model or dataflow that's already published in the Power BI Service. The error "You don't have permissions to the underlying external dataset" means you lack the specific Build permission required for that foundational dataset, even if you have general access to the workspace it resides in. Think of it as having a key to the main building but not the specific locked room inside that your report needs to access. This is why Power BI prompts for a DirectQuery connection; it's trying to talk to that external model and failing due to this permissions gap.

To fix this, you first need to identify the exact source dataset. You can do this by opening the Power Query Editor in your PBIX file, selecting the problematic table, and looking at the Source step in the Applied Steps pane. This will show you the name of the underlying semantic model and its workspace. Once you've identified it, you will need to contact the owner of that source dataset and ask them to grant you Build permission. They can do this by navigating to that dataset in the Power BI Service, selecting "Manage permissions," and adding your account.

After you have confirmed that the correct permissions have been granted, the final step is to refresh your credentials within Power BI Desktop. Go to File > Options and settings > Data source settings. Find the connection that points to the Power BI dataset, select it, and click Clear Permissions, then Edit Permissions to sign in again. This action forces Power BI Desktop to re-authenticate with your newly updated access rights. Once this is done, the connection should be re-established, allowing you to access the table and disable its load as you originally intended, resolving the refresh issue without having to rebuild your report.

Best regards,