Hi all,
Here's the situation, we have Dev, Test and Prod environments. The developer is currently the owner of the flows in Dev and another user is the owner of the flows in Test and Prod. We use a DevOps pipeline to deploy between the different environments. It's a third person who carries out the deployment. What we are seeing is that everytime a flow is modified in the dev environment, when it is deployed to test it becomes deactivated and the connection has to be reset. This means that the person in test has to modify the flow to activate it and re-establish the connection which in turn creates an unmanaged layer on the flow which has to be deleted in order for the modifications to show up. Basically a whole lot of manual steps that we would love to avoid.
I have seen that connection references can now be set during deployment using a settings file: https://docs.microsoft.com/en-us/power-platform/alm/conn-ref-env-variables-build-tools We have tried this and it doesn't seem to be doing anything, our flows are still deactivated and no connections are set. The connection references say they have been modified, but no change to the flows themselves. Any tips on how to get this to work?
I have seen a lot of people having issues like this but no clear answers to why or how to solve it. I imagine it is to do with the multiple users involved across our environments. Unfortunately, it doesn't seem possible (correct me if I'm wrong) to use a service principal as owner of our flows as we will quickly reach API call limits.
Any ideas of what we need to do to get the flows to stay active and for the connection to be set during deployment? I'm grateful for any insight.
