"The import PowerPlatform.Dataflows matches no exports"-error on existing dataflows

[joakims]

I have an issue trying to fix existing dataflows (gen1). I get the error message:

"The import PowerPlatform.Dataflows matches no exports. Did you miss a module reference?

Details

Reason = Expression.Error

ErrorCode = 10079"

Also, the "Source"-step in "Applied steps" is greyed out. In short, it seems as if Power BI service cannot find the dataflow-connector, which should be built-in and supported.

If i replicate the exact same query in a new dataflow (create new gen 1 or gen 2) - it works.

Please fix the issue causing existing dataflows to be non-fixable, as rebuilding everyting would be time consuming to an extreme degree.

BR,

Joakim

[joakims]

The issue seems to have been resolved

[powerBiUser_VL]

The issue is still there after 14/07/2025 update. The extension of PowerPlatformDataflows.pqx is not available in the latest release.

[MaAl]

We have still the same issue. It looks like there is only the dataflow legacy connector available now and you have to rewrite the M-Code using this legacy connector. Is this an issue? Is the legacy connector stable?

Not working M-Code: let Source= PowerPlatform.Dataflows(null),...

Working legacy M-Code: let Source= PowerBI.Dataflows(null),...

[asocorrocognex]

Same issue for me.  Only legacy connector available:

[KennyD]

Same issue... Im not eager to change it to the legacy M-code... i presume its a bug The dataflows on the service environment still work... its when creating a new semantic model that this gives me an error

[asocorrocognex]

I noticed the error when I opened an existing Desktop report.

[aJaySulmara]

Also experiencing this issue now on critical business reports. I can't believe that there has been no communication that this connector is being removed, or that there is an obvious bug...!!

[asocorrocognex]

It seems fixed now.

[cmcnally]

I having the same issue. I updated the source step to '= PowerBI.Dataflows(null)' but the Navigation step is still broken. When I add a new table from the dataflow, the Navigation step is exactly the same as the old broken one

[MaAl]

you have to adjust the navigation step after changing to legacy code. click on the settings symbol at the navigation step and navigate to your dataflow. But obvisouly it's a workaround rather then a fix.