Forum Discussion
Super UserDataflow gen2: use libraby variable for destination ?
Super UserHello v-ssriganesh
What I don't understand,
I modified the .PQ via OneLake explorer, as it doesn't work,
I decided to use the API approach, but when I get my PQ definition via the API, I can see the modification I've done via the one lake Explorer, in the destination source I have:
Navigation_2 = Navigation_1{[warehouseId = Variable.ValueOrDefault("$(/**/Variables_1/Warehouse_ID)", "1f5196d3-59a1-41b1-9fee-9900c1eXXXXX")]}[Data]
So it means that OneLake explorer is able to modify my files ?
I just republish the dataflow via API and I see an improvement, as a a warehouse, I have nothing:
But it continues to load it in the wrong table
Community SupportHi Cookistador,
Thank you for the additional details.
Yes, OneLake Explorer can modify the .pq file, and that’s why the REST API shows your updated M script. However, in Dataflow Gen2 the destination is not controlled by the M script. It is stored in separate metadata, which is not updated when you edit the .pq file.
So even though your Navigation step changed, the Dataflow still loads into the old table because the destination metadata was never updated. Republishing via API only refreshes the script. it does not overwrite the destination settings.
To actually change where the data is written, you must update the destination/output configuration through the Fabric REST API or via Git deployment. Editing .pq alone will not redirect the load.
- Cookistador
Ok so if I undestand correctly
I have to use the API to get the .pq files coded in Base64, then I have to Decode it, update it with the parameter I want to use and after that, I use the API to update my new flowIs it right?
Not possible to do the same in file explorer even if I edited the Mashup File AND the DataflowEditingSession ?I'm just looking for an easier workaround for my business team 😕
- v-ssriganesh
Hello Cookistador,
As per my knowledge, the only supported options today for changing the destination are the REST API and Git-connected workspaces. If this capability is important for your business users, We recommend submitting it to the Microsoft Fabric Ideas forum. This helps the product team track demand for improving Dataflow Gen2 authoring and making destination updates easier without relying on the API.
Ideas link: https://ideas.fabric.microsoft.com
- v-ssriganesh
Hello Cookistador,
Could you please confirm if you've submitted this as an idea in the Ideas Forum? If so, sharing the link here would be helpful for other community members who may have similar feedback. For any further discussions or questions, please start a new thread in the Microsoft Fabric Community Forum, we’ll be happy to assist.Thank you for being part of the Microsoft Fabric Community.