Error "[403.12–403.30] The name 'Lakehouse.Contents' does not exist in the current context"

[_David_]

I'm encountering the following error when trying to connect to a Dataflow using the Dataflow connector in Power BI:

The name 'Lakehouse.Contents' does not exist in the current context.

This happens when attempting to access a Dataflow that is stored in a Microsoft Fabric environment, specifically within a Fabric workspace.

Context:

• I'm using the Dataflow connector in Power BI Desktop.
• The Dataflow is created and stored in a Fabric workspace (not a legacy workspace or classic Power BI workspace).
• The error appears immediately after selecting the Dataflow and trying to load or transform the data.

Troubleshooting so far:

• Verified permissions to the workspace and the Dataflow.
• Confirmed that the Dataflow is published and accessible via the Fabric UI.
• Tried using both organizational and personal accounts for authentication.

Question:

Has anyone else experienced this issue when working with Dataflows in Fabric environments? Is there a known workaround or update needed to support this connector in Fabric?

Any insights or suggestions would be greatly appreciated!

Thanks in advance,
David

[ChrisH-94]

I have had the same issue and have not been able to find a workaround.

[fabric_analyst_]

same issue since this weekend.

[ChrisAleman]

My team and I have the same issue when refreshing reports connected to Gen2 dataflows in desktop- so far it's all of our dataflows, not a select few. Same reports, no issues refreshing in desktop prior to yesterday. When we publish the same report in service, we are able to refresh using service- seems to be isolated to desktop. No changes in admin settings- confirmed with IT. Also, we opened excel and are able to connect successfully to the same dataflows that are causing the error in PBI desktop. [403,12-403,30] The name 'Lakehouse.Contents' doesn't exist in the current context.

[ChrisAleman]

After some investigating, there was a new PBI desktop update released 2 days ago on the 14th. All but one team member had their PBI desktop updated to the latest version and 1 team member is a version behind- he is the only one that is able to refresh without any issues. It appears to be an update issue- waiting to confirm timeline of update installs to confirm my hypothesis.

[nmw186]

Adding to Chris' comment above. Issue is present here in powerbi desktop 2.145.1105.0 the update was pushed to this system today.

[stipa]

I also having the same issue with all my dataflows using PowerBi Desktop

[Marlon_Muoz]

Same issue with dataflows. Did not find a workaround yet.

[tmartin]

I submitted a ticket and Microsoft acknowledged that it is a bug with the July release. They told me to roll back to June temporarily until it is resolved. Here is a link to download the June version... https://learn.microsoft.com/en-us/power-bi/fundamentals/desktop-latest-update-archive?tabs=powerbi-d...

[stipa]

@tmartin I tried downloading the previous version, but it keeps redirecting me to the latest release. Is there a way to download the earlier version instead?

[accowize]

Hi all, Since today I've been getting this when refreshing any query to a dataflow:

[403,12-403,30] The name 'Lakehouse.Contents' doesn't exist in the current context.

Refresh works fine online in service.  It is in Power BI Desktop that it fails.

Is there a fix to this bug? Important!