We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hey Everyone,
I have been using Dataflows for an API intergration for the last 2 months. Since the full release of the service i can no longer save a change. The M Function is the same but now i get this error,
"Your dataflow can't be saved because one or more entities references a dynamic data source"
Can anyone help?
Thanks
Darren.
Same issue for me
Hi,
The solution in this post worked for me: https://community.powerbi.com/t5/Service/Dataflow-use-of-M-function-turns-workspace-into-Premium-cap...
It seems that putting the variables in a RelativePath argument avoids the dynamic data source error.
Hi, thanks for the hint.
unfortunately i am also not able to save the data flow cause due to the dynamic data set message when I try to save a function. It is a dedicated instance with the diamon. Any help highly appreciated.
Hi @Anonymous ,
Based on my test, I cannot reproduce your issue here. I suggest you to refer to this third party bolg to work on Computed Entity. If it doesn't help, kindly create a support ticket for help here.
Thanks, I have logged a support ticket. I will update here once i have an answer. 🙂
Hi,
I am currently struggling with the same issue. Did you find a solution?
Regards,
Steffen
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.