Forum Discussion

_David_'s avatar
_David_
Icon for Advocate I rankAdvocate I
1 year ago

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

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

Dataflow

34 Replies

  • vikramkumawat's avatar
    vikramkumawat
    Icon for Advocate II rankAdvocate II
    1 year ago

    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!

    • fabric_analyst_'s avatar
      fabric_analyst_
      New Member
      1 year ago

      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's avatar
      vikramkumawat
      Icon for Advocate II rankAdvocate II
      1 year ago

      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's avatar
        v-kpoloju-msft
        Icon for Community Support rankCommunity Support
        1 year ago

        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.

    • _manu_'s avatar
      _manu_
      Frequent Visitor
      1 year ago

      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

  • Anthony_G1's avatar
    Anthony_G1
    Frequent Visitor
    1 year ago

    I'm experiencing this same issue this morning - is there an outage of some kind currently?

    • dataflip's avatar
      dataflip
      Icon for Kudo Kingpin rankKudo Kingpin
      1 year ago

      Yes, you’re right this issue seems to be related to Expression.Error: Lakehouse.Contents doesn't exist, as mentioned in the Microsoft Fabric Community thread. I agree that it makes sense to combine this with that discussion to avoid duplication and track any official resolutions or updates in one place.

  • bhofbauer's avatar
    bhofbauer
    New Member
    1 year ago

    Same issue. Do we have an update from MS on if they are aware of the problem and working toward a fix?