Dataflow selecting destination

[fabric_1]

Hi, I am transforming data using fabric dataflow gen 2 and while selecting destination, I can choose the target lakehouse only under a workspace(dev), if I deploy the dataflow in a pipeline to prod then how can I repoint the destination to lakehouse under prodworkspace automatically?

Kindly help!

[v-sgandrathi]

Hi @fabric_1,

Thank you for using Microsoft Fabric Community Forum.

Since you're using Fabric Dataflow Gen2 and want to automatically repoint the destination Lakehouse when promoting from a Dev workspace to Prod, the right approach is to use a Deployment Pipeline in Microsoft Fabric.

Within the Deployment Pipeline, you can set up a deployment rule to override the destination Lakehouse specifically for the Prod stage. This allows the dataflow to dynamically connect to the correct Lakehouse based on the environment without needing to manually edit the dataflow each time. This setup ensures a smooth, automated transition across environments.

If my response was helpful, consider clicking "Accept as Solution" and give us "Kudos" so that other community members can find it easily. Let me know if you need any more assistance!

Thank you.

[prvackouc]

There are no options to set deployment rules on Fabric Dataflow Gen2, at least none that I can see in my 'Dataflow Gen2 (CI/CD, preview) deployment rules' sidebar: 

Is that by design? If yes, why did you recommend a solution that does not exist?

[v-sgandrathi · Accepted solution]

Hi @prvackouc,

You're absolutely right to question it. Currently, Dataflow Gen2 in Microsoft Fabric does not support deployment rules, which is why you’re not seeing any options in the deployment rules pane. This is by design in the current preview phase, and unfortunately, destination lakehouses cannot be dynamically repointed via deployment rules at this time.

The earlier suggestion assumed this feature would be available similarly to other deployable items, and I appreciate you catching that. For now, manually updating the destination Lakehouse after promotion remains the recommended approach. If Microsoft adds support for deployment rules in Dataflow Gen2 in future updates, that should help automate this process more smoothly.

Thank you.

[v-sgandrathi]

Hi @fabric_1,

May I ask if you have gotten this issue resolved?

If it is solved, please mark the helpful reply or share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster.

Thank you.

[v-sgandrathi]

Hi @fabric_1,

I wanted to follow up on our previous suggestions regarding the issue. We would love to hear back from you to ensure we can assist you further.

If our response has addressed your query, please accept it as a solution and give a ‘Kudos’ so other members can easily find it. Please let us know if there’s anything else we can do to help.

Thank you.

[lbendlin]

 if I deploy the dataflow in a pipeline to prod

A fabric pipeline or a deployment pipeline?

[fabric_1]

Fabric pipeline