Forum Discussion
Advocate IPower BI Desktop - Dataflow - The name 'Lakehouse.Contents' does not exist in the current context.
Advocate IIHello 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!
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.
- 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-msftCommunity Support
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.I'm not in the East US and have been encountering the issue.
Hello,
(Sorry for my broken English...)
I have the same problem: the Lakehouse.Contents([]) connector no longer seems to be recognized!Power BI Desktop Version :
Version: 2.145.1105.0 64-bit (July 2025)Everything was still working yesterday morning (July 15) at 9:00 AM (French time).
Here is the list of Microsoft Fabric connectors currently available in Power Query: many are missing!
Thanks in advance,
Manuel
We have the same issue. Microsoft, please fix!
- 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 LearnHope 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.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.
I also see the same as _manu_ in Power BI. The Lakehouse (Preview) connector is not available.
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.
- HarishKM
Super User
vikramkumawat Hey,
I will troubleshoot this in below stepss1- Go to the data lake or Power BI environment and confirm the lake house content (tables, files, or datasets) exists and is accessible.
s2- I will verify that the names, paths, or dataset IDs used in the dataflow or connector are accurate and up to date.
s3- I will also make sure my user account has proper permissions to access the data lakehouse content.
Thanks
Harish M
Please accepts this as a solution if it is solve your problem and give kudos as well
- vikramkumawat
Hi HarishKM ,
Thank You for your response. Actually I am using this report from past few months and nothing is changed, in data source and access permissions. also in febric it is working fine like scheduled refresh working properly with same creds and same data sources. but when i download that and try to refresh this in local with same creds its giving the error.
- rohit1991
Hi vikramkumawat ,
This error means the Lakehouse.Contents connector is either missing or not recognized in your current Power BI or Fabric environment. This often happens due to either recent service changes or outages in Microsoft Fabric or Updates or breaking changes to the connector or permissions or Attempting to use a Fabric-only function in classic Power BI Desktop or unsupported environments.
To fix the issue you can start by Checking the Fabric Service Health by going to the Power BI/Fabric Support page to see if there are any ongoing incidents affecting Lakehouse or Dataflows. Then update Power BI Desktop as connector support is updated frequently. Validate Permissions: Double-check that your user account still has access to the Lakehouse and Dataflows in Fabric. Restart and Reconnect: Close and reopen Power BI/Desktop, and try reconnecting to the Dataflows. Microsoft Community & Docs: Fabric documentation on Lakehouse connector- vikramkumawat
Hi rohit1991 ,
Thank You so much for your response, Yes I tried the refresh in a different system with PBI Desktop June 2025 version in that it refreshed without any error. but in my system it is July version. I am not sure if it can be possible that it is happing due to the update or anything else is happning, because to refresh I used same creds and same network, just the difference was PBI Desktop version.
If the issue is with version only then is it possible to install older versions of PBI Desktop ?Thanks.
- rohit1991
Hi vikramkumawat ,
It definitely sounds like this issue is related to the July 2025 Power BI Desktop update, especially since the same dataflow refresh works perfectly on the June version with identical credentials and environment.
Yes, you can install an older version of Power BI Desktop:
-
Uninstall your current version first.
-
Download and install the June 2025 (or any previous) version from the official Power BI Desktop archive.
-
I am also facing the same issue. Microsoft, please fix!
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)
Using the Power Platform > Power BI dataflows (Legacy) connector works though.
Update: actually selecting a table in the dataflow failed.
I am able to successfully connect to our gen2 dataflow this morning using the normal Dataflows connector.
