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!
Community SupportHi 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.
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.
