Forum Discussion
Dataflow and PowerBI Gateway - Sourcing data dynamically
This is good news for me. Depending on the release date, of course. Sooner would be better... 😁
(I suspect a Pipeline will facilitate the dynamic sourcing more easily than the Dataflow.)
The internal team has confirmed that, there is no dynamic ability to switch between different databases today. The connections themselves must be validated and are thus static for this reason.
I hope this helps. Please do let us know if you have any further questions.
Thanks
- AndrewWestran2 years agoHelper I
I appreciate that the connection would need to be validated and static. However, I would hope that database selection within the context of a static connection could be dynamic. Privileges from the established connection would apply.
I also appreciate that this would introduce levels of complexity to the static mechanisms of the Dataflow which are hard-wired to a particular table for example, to which the transformation steps would be applied.
It feels like this would be an ideal application of the Notebook capabilities, for example, to select a data source and manage the data definition, sourcing, and push to the final destination in code, rather than using a graphical tool.
Thanks
- Element1152 years agoMemorable Member
Can you migrate some of the data to a lakehouse? Perhaps an aggregate version of the source data? Storage cost is very inexpensive from what I've seen.
- AndrewWestran2 years agoHelper I
Thanks for your comment, Element115.
To manage this migration to the lakehouse without the dynamic DB access capability, we would need to move the functionality to the source system, e.g., export the data to Azure Blob storage and then import it into the lakehouse.
This is our only alternative at this point and is unnecessarily complicated, where Fabric touts a unified toolset, which falls short in this scenario.