How to use variable library for deployment from Test to Prod?

Hello Anonymous,

You’re right, you can use the Variable Library to parameterize both the source connection string and the destination when working with Pipelines or Notebooks. This is the recommended approach if you want to fully automate deployment from Dev → Test → Prod.

For Dataflow Gen2, there are still some limitations:

• You can parameterize the source (server, database, schema, table, etc.) directly in Power Query M using variables.

• But the destination (sink) can’t be parameterized with variables — it must be defined at design time and adjusted manually after deployment.

Docs:

- Variable library integration with Dataflow Gen2

- https://learn.microsoft.com/en-us/fabric/cicd/variable-library/variable-library-overview

- https://learn.microsoft.com/en-us/fabric/cicd/variable-library/tutorial-variable-library

Hope it can help you ! 

Best regards,

Antoine

HI Anonymous,

Have you had a chance to review the solution we shared by AntoineW ? If the issue persists, feel free to reply so we can help further.

Thak you.

Hi Anonymous,

Checking in to see if your issue has been resolved. let us know if you still need any assistance.

Thank you.

I created a simple table and stored it in a Lakehouse using Dataflow Gen2. Then, I used this Lakehouse as a data source. After defining my variables in the Variable Library, I configured the Pipeline dynamically so that it uses a dynamic source and destination address — and it works successfully.

However, I would like to know whether it’s possible to add this logic directly in the query code (M language), so that I wouldn’t need to use a Copy Data activity in the pipeline during deployment.

Thank you very much for your support!

Hey, 

It could be great that Dataflow Gen2 destination  have the same implementation as Copy Job.

It seems the best way to use.