Forum Discussion
GUIDANCE::Query causing "Dynamic datasources not supported" error
You can have a query that uses #shared or #sections in a Dataflow Gen2, but since these are dynamic queries in order for them to not cause any issues you need to make sure that they're not set to be loaded anywhere not are they set to be staged.
What's missing today in the Power Query Online experience is the ability to see the full description and documentation of the function. We're internally tracking this gap between the legacy Power Query Desktop UI experience and the new one found in Power Query Online.
Be sure to post the idea in aka.ms/FabricIdeas to help us prioritize this gap, but the behavior that you're seeing today on how the dataflow behaves with a dynamic query like that is by design. If you have any porposals to change this by-design behavior, please be sure to suggest it in the Ideas Portal as well.
Best!
You can have a query that uses #shared or #sections in a Dataflow Gen2, but since these are dynamic queries in order for them to not cause any issues you need to make sure that they're not set to be loaded anywhere not are they set to be staged.
What's missing today in the Power Query Online experience is the ability to see the full description and documentation of the function. We're internally tracking this gap between the legacy Power Query Desktop UI experience and the new one found in Power Query Online.
Be sure to post the idea in aka.ms/FabricIdeas to help us prioritize this gap, but the behavior that you're seeing today on how the dataflow behaves with a dynamic query like that is by design. If you have any porposals to change this by-design behavior, please be sure to suggest it in the Ideas Portal as well.
Best!
By the way, are you by any chance the co-author of 'Master your data with Power Query'?
I am. Yes.
Awesome! Great book btw, which I recommend to everyone. Now we need a book that teaches how to program in M, especially all the esoteric tricks of functional programming applied to table processing because the Microsoft documentation is unfortunately not even the bare minimum.