Forum Discussion
Dataflows DeltaLake.Table Module Reference Error
Hello!
I am trying to replace current datawarehouse connections with new cloud connections of my existing dataflows, but encounter this error message: The import DeltaLake.Table matches no exports. Did you miss a module reference?
However, I am actually able to use the DeltaLake.Table() function on a NEW dataflow, without getting this module reference error:
(data loads just fine using the DeltaLake.Table function, when i it was a new dataflow created)
And so, the reason I'd like to replace the original DW source, is to easily transition from on-premise connections to the cloud connections. However, this module reference is causing a problem...
Is there a way to "update" the old dataflows for them to have the module installed in a way?
I would definitely prefer this solution, otherwise, it would be checking all power bi reports, replace the old dataflows with new dataflows, which would be a tedious task...
-----
d_HCMWorker is the existing dataflow, which I would like to have the cloud connection, which gives the module reference error
d_HCMWorker_CLD is the NEW dataflow meant to show that it is possible to load data using the DataLake.Table() function
Hi MatthewBI ,,
Based on the error message you provided, it could be caused by power query not being able to titrate to a specific module, in the old data stream of not updating your data in time. That's why you were able to get the data after recreating the new data stream.
To update the data stream more easily, you can download the JSON file of the existing data stream, modify it to include the new module, and then reimport it.
You can refer to the following documentation for detailsUnderstand and optimize dataflows refresh - Power BI | Microsoft Learn
Dataflows best practices - Power BI | Microsoft LearnBest regards,
Albert HeIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly
1 Reply
Hi MatthewBI ,,
Based on the error message you provided, it could be caused by power query not being able to titrate to a specific module, in the old data stream of not updating your data in time. That's why you were able to get the data after recreating the new data stream.
To update the data stream more easily, you can download the JSON file of the existing data stream, modify it to include the new module, and then reimport it.
You can refer to the following documentation for detailsUnderstand and optimize dataflows refresh - Power BI | Microsoft Learn
Dataflows best practices - Power BI | Microsoft LearnBest regards,
Albert HeIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly