Forum Discussion
Dataflow gen2: use libraby variable for destination ?
Hi Cookistador,
Thank you for posting your query in the Microsoft Fabric Community Forum.
At the moment, Dataflow Gen2 does not support changing the destination output settings by manually editing the mashup script in OneLake. Even though the files appear in OneLake File Explorer, they are not the source of truth for Dataflow Gen2. The product currently ignores manual edits because:
- Destination configuration is stored as metadata, not in the mashup script.
- Editing the script in OneLake does not trigger a metadata refresh, so the UI continues to show and use the previous destination.
If dynamic destination configuration is important for your scenario, we recommend using the Fabric REST API or Git connected workspace, as these are supported approaches for parameterizing destinations.
Best regards,
Ganesh Singamshetty.
Hello 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