Please enable Dataflow Gen2 destination parametrization. We would like to parametrize the path/table in destination Lakehouse.
Mauro89, For me, this problem was solved by the introduction of the !(Current workspace) feature. (Workspace ID = "."). I keep my related dataflows and lakehouses (Bronze, Silver, Gold) in one workspace and use !(Current workspace) everywhere in the Gen2 dataflows for source and destination. Implementation from Development to Acceptance to Production in the implementation pipeline now works without a problem and I never need to make changes in git anymore.
