Community AdminHi!
Our recommendation is to adopt either one of the approaches from the article below:
CI/CD and ALM solution architectures for Dataflow Gen2 - Microsoft Fabric | Microsoft Learn
The closest would be to use Fabric variable libraries which Dataflow Gen2 fully supports.
The benefits of this approach over the delployment rules is that from a Git perspective you are not affecting the actual mashup document. This means that the deployment is really just copying the same Dataflow from one environemnt to the next and the variables are the one passing the correct values for execution, but they simply remain as variables.
The bad effect of using deployment rules was that each deployment would trigger 2 changes:
1. Updating the content of the mashup document of the Dataflow with the one from the earlier environment
2. Doing a sort of "find and replace" over the outcome of #1
This behavior would actually go against some principles of how ALM should be handled that the exact code that you tested in your earlier environment is just being pushed to a different environment because #2 fundamentally changes that code.
Hope this helps!
