Lakehouse.Contents bug in pbi desktop?

[JonasArnout2]

Is there a bug in the latest update of pbi desktop?

recently i get this message using the PQ function Lakehouse.Contents

Earlier this has worked just fine.

There is a workaround loading the date through the sql endpoint, but the sql endpoint is ugly and you need to include the lakehouse name instead of the id ... the name can be changed i think ....

Expression.Error: The import Lakehouse.Contents matches no exports. Did you miss a module reference?

[v-hjannapu]

Hi @JonasArnout2,
Thank you for posting your query in Microsoft Fabric Community Forum. Also, thanks  to @lbendlin , @rohit1991 

for those inputs on this thread. 

The issue you are facing with Lakehouse.Contents not working is likely due to recent changes in the latest Power BI Desktop update. This function is part of the Microsoft Fabric connectors, and sometimes it may break if the right module is not loaded or if preview features are not enabled.

To fix this, please make sure you're using the Power BI Desktop (Optimized for Fabric) version. Also, go to File > Options > Preview features and check if Microsoft Fabric Integration is turned on. After enabling it, restart Power BI and try again.If that doesn’t help, your current workaround using the SQL endpoint is fine for now, but I agree  using the name instead of the ID is not ideal since names can be changed.
Kindly refer to the below documentation links for better understanding:
https://learn.microsoft.com/en-us/power-query/connectors/lakehouse 

Hope the above provided information help you resolve the issue, if you have any further concerns or queries, please feel free to reach out to us.
Regards,
Harshitha.

[v-hjannapu]

Hello @JonasArnout2,
I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.

Regards,
Harshitha.

[lbendlin · Accepted solution]

From Microsoft:

Updates

• Jul 15, 2025, 8:00 PM EDT

   

  The change reversion has completed and we've confirmed through service health telemetry that impact was remediated. To fully restore service, users will need to restart their desktops.

[rohit1991]

Hi @JonasArnout2 ,

Yes, you are correct, there appears to be a bug with the Lakehouse.Contents function in the latest Power BI Desktop update (July 2025). Multiple users have reported that Lakehouse.Contents, which previously worked, now throws errors. This issue is new in the July 2025 release and is not present in earlier versions like June 2025.

Workarounds:

• Use the previous version: Uninstall the July version and install the June 2025 version from the official Power BI Desktop archive.

• SQL endpoint: As you mentioned, you can use the SQL endpoint, though it may require adjusting queries and isn’t as straightforward.