Pipeline source control issue: Dataflow Gen2 pipelines overwrite dataflowId with logicalId

Hi DarSz ,

Thank you for reaching out to the Microsoft fabric community forum. We understand the challenge you’re facing this behavior significantly impacts CI/CD workflows across multiple environments.

At present, Dataflow Gen2 pipeline activities do not support parameterized or dynamic values for workspaceId and dataflowId. When changes are committed to source control, Fabric replaces these values with the logicalId and a placeholder workspace ID by design. This limits the ability to use Dataflows reliably in multi-environment CI/CD deployments.

Your workaround of using Notebooks is a valid approach, and many customers adopt this path for scenarios where Dataflow Gen2 is not yet fully supported. Currently, there is no published ETA or roadmap commitment on enabling parameterized deployment of Dataflow Gen2 pipeline activities as mentioned by Vinodh247 .

As a further steps, I’d recommend:

• Submitting and upvoting feedback on the Fabric Ideas - Microsoft Fabric Communityso that this scenario can be prioritized.
• Tracking the Microsoft Fabric Roadmap for updates on Dataflow Gen2 pipeline activity improvements.

Dataflow Gen2 activities may not fit well in CI/CD processes today, and Notebooks or alternative orchestration methods are the recommended option until more flexible deployment support is introduced.

Hope this helps, please feeel free to reach out for any further questions.

Thank you.