Power BI Desktop - Dataflow - The name 'Lakehouse.Contents' does not exist in the current context.

[_David_]

Hi everyone,

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

[vikramkumawat]

Hello Everyone,

I'm encountering an issue while trying to fetch data from dataflows. I have created these dataflows in Microsoft Fabric and am accessing them via the Power Platform Dataflows connector.

This approach has been working fine for the past few months, but starting today, all tables are showing errors, and I'm unable to retrieve any data.

Has anyone else faced this issue recently, or is there a known solution or workaround?

Any help would be greatly appreciated.

Thank you in advance!

[Jeroen_Geenen]

Just tried to refresh again this morning and it is working now for me! Thank you, engineering team...

[vikramkumawat]

Hello Everyone,

An official notification regarding this issue has been posted on the Microsoft Fabric support site: https://support.fabric.microsoft.com/en-IN/support/.

The Microsoft team is actively working on resolving the issue. In the meantime, as a workaround, we can downgrade to the June 2025 version (or an older version) of Power BI Desktop until a permanent fix is in place.

Thanks

[v-kpoloju-msft]

Hi @vikramkumawat,

Yes, you are right this issue has been officially acknowledged on the Microsoft Fabric support site. As noted in the advisory, customers in the East US region may experience issues while executing queries in their Lakehouse’s and Data Warehouses.

The engineering team has already identified the root cause and is actively working on deploying a fix.

Thank you for highlighting this. As a temporary workaround, downgrading to the June 2025 version of Power BI Desktop (or earlier) has been found helpful for affected users.

We will continue to monitor the situation and update this thread if anything changes. Appreciate your patience and collaboration.

Thank you for using the Microsoft Fabric Community Forum.

[v-kpoloju-msft]

Hi @vikramkumawat,

Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.

Thank you.

[chris_drabek]

Thank you for following up.  The issue cleared up the next day and has been working since.

[chris_drabek]

I'm not in the East US and have been encountering the issue.

[ShrirajSPatil]

Notification DateTime: 07/16/2025 16:52 PDT | Resolved Time: 07/16/2025 20:29 PDT

Fabric customers in East US region may have experienced issues while executing queries in their Lakewarehouses and Datawarehouses. Engineering team investigated and applied relevant mitigations to mitigate the issue.

[v-kpoloju-msft]

Hi @vikramkumawat,

Thank you for posting your query in Microsoft Fabric Community Forum. Also, thanks to @bhofbauer, @chris_drabek, @fabric_analyst_, @rohit1991, for those inputs on this thread. Here I provided some official Microsoft links those might be helpful to resolve your thread more quickly

Based on the error you are getting (Lakehouse.Contents does not exist), it seems like your query contains code specific to the Fabric Lakehouse environment, which may no longer be supported (or was never officially supported) through the Power Platform Dataflows connector.

To fix this:

• If you are trying to access Fabric Dataflow Gen2 outputs, switch to using the Lakehouse (Preview) connector in Power BI Desktop.
• Avoid using the Lakehouse.Contents function directly in Power B, it is not recognized in that context.
• Try connecting through the OneLake Data Hub or using DeltaLake.Table if accessing files from OneLake.

Kindly refer to the below documentation links for better understanding:
Power Query Lakehouse (Beta) connector - Power Query | Microsoft Learn
Power Query Dataflow connector - Power Query | Microsoft Learn

Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.

Thank you for using the Microsoft Community Forum.

[_manu_]

Hello @v-kpoloju-msft , and thank you for your reply.

Perhaps there was a misunderstanding regarding our issue?

Indeed, you are recommending the use of the Lakehouse connector, but the problem is precisely that this connector no longer appears to be available in Power Query / Power BI Desktop (July 2025 version), as you can see in the screenshot below (in French, sorry), which lists all available Fabric connectors:

As you can see, many connectors are missing compared to the screenshot shown on Microsoft Learn, copied below : 

Here is another screenshot showing a search for the term “Lake” – no result at all!

I would also like to point out that the same query runs perfectly fine in the Power BI service: the expression Lakehouse.Contents()  is fully recognized and functional in that context.

Could you please ensure that this bug is addressed and resolved as soon as possible?

Thank you in advance.

[chris_drabek]

I also see the same as _manu_ in Power BI.  The Lakehouse (Preview) connector is not available.

[bhofbauer]

Same issue for me. Any updates from MS on if they are aware or planning a fix?

[chris_drabek]

I am having the same issue when connecting to Gen2 Dataflows using the Dataflows connector in PowerBI Desktop.  Reports running in the service using the same Dataflows refresh without issues.

Version: 2.145.1105.0 64-bit (July 2025)

[chris_drabek]

Using the Power Platform > Power BI dataflows (Legacy) connector works though.

Update: actually selecting a table in the dataflow failed.

[chris_drabek]

I am able to successfully connect to our gen2 dataflow this morning using the normal Dataflows connector.

[fabric_analyst_]

can't microsoft just roleback to june version and release july version after doing proper testing?

all of our reports use dataflows gen2 and our dev teams are using power bi desktop.

[ruiz07s]

Same issue here, never had this error before just came out of nowhere today.

[Martins1234]

The same issue here

[JeremyCoward]

I have the same issue. It's causing big problems. 

[raktnk]

Reporting the same problem.

It was working normally on version 2.144.1378.0 (June 2025) and after updating from the Microsoft Store to version 2.145.1105.0 (July 2025) it began returning the error "[403.12–403.30] The name 'Lakehouse.Contents' does not exist in the current context"