Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply

Error Message dataflow gen 1

Hi,

 

Since today I get the following error message when refreshing my dataflows gen 1: "Expression.Error: The import PowerPlatform.Dataflows matches no exports. Did you miss a module reference?"

Any idea what is wrong? Something changed?

 

Jochen

5 REPLIES 5
v-agajavelly
Community Support
Community Support

Hi @jochendecraene ,

Just checking in glad to hear you were able to identify the connector name change and get things working again. That kind of silent shift from PowerBI.Dataflows(null) to PowerPlatform.Dataflows(null) can definitely be tricky to spot.

Were things still running smoothly after switching it back? Sometimes those subtle backend updates catch us off guard, so just wanted to make sure everything's stable now.

Reagrds,
Akhil.

v-agajavelly
Community Support
Community Support

Hi @jochendecraene ,

Thank you for confirming and sharing the screenshot.

It’s quite insightful that the connector name had changed locally from in csharp

= PowerBI.Dataflows(null)

to

= PowerPlatform.Dataflows(null)

This kind of silent change often happens due to backend updates or connector reconfigurations by Microsoft. Good call on switching it back to PowerBI.Dataflows(null)  glad to hear that resolved the issue and your dataflow is now loading correctly.

If @BeaBF  response helped guide you toward the solution,

If the above solutions works consider marking it as “Accept as Solution” and give a kudos to help others in the community facing the same Gen1 connector issue.

Regards,
Akhil

BeaBF
Super User
Super User

@jochendecraene Hi! 

Looks like Microsoft made a backend change affecting the PowerPlatform.Dataflows connector for Dataflows Gen1. The error "Expression.Error: The import PowerPlatform.Dataflows matches no exports. Did you miss a module reference?" typically means that the M engine can no longer find the library it’s trying to load.

This is likely part of Microsoft’s gradual phase-out of certain Gen1 connectors in favor of Dataflows Gen2. You’ll want to check your environment to see if the connector is still supported, or plan to switch to the newer Dataflows or OData connectors depending on your setup.

 

Try to check your dataflow connectors:

In Power BI Service → Settings → Manage Gateways → Data Source Settings

Confirm whether the PowerPlatform Dataflows connector is still available and/or if there's a new version.

 

BBF


💡 Did I answer your question? Mark my post as a solution!

👍 Kudos are appreciated

🔥 Proud to be a Super User!

Community News image 1920X1080.png

This is strange. It seems like the name changed from = PowerBI.Dataflows(null) to = PowerPlatform.Dataflows(null) in my local report in Power Query. When I change it back to = PowerBI.Dataflows(null) to go to the desired workspace via M and navigate manually, it does work to load the dataflow.

@BeaBF  Thnx for the quick response

 

I see two type of dataflows, both are online 

connectors.jpg

Helpful resources

Announcements
July 2025 community update carousel

Fabric Community Update - July 2025

Find out what's new and trending in the Fabric community.

July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.

Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

Top Solution Authors
Top Kudoed Authors