Power Platform Community Forum Thread Details

I have 3 solutions using common custom connections, connection references and flows. I was getting error while committing to git saying solution binding scope cannot have same component in multiple solutions. Hence I have created a separate solution which has now all the common connections, connection references and flows being used by copilot agents in other 3 solutions (removed common components from these 3 main solutions ). I am now able to commit the changes without error and also deployed all 4 solutions as managed solution in Test environment and tested flows through agents successfully. Is this a correct approach to manage common components as I see those removed components as missing dependencies in

missingdependencies.yml in repository.

Categories:

General topics

This is the better approach because when the same component is used across multiple solutions, one would typically expect the behavior to be determined by the most recently deployed solution. However, it works differently. Instead of considering the last deployment, the behavior is governed by the solution layer of the component.

For example, consider three solutions: SolA, SolB, and SolC.

Initially, SolA is deployed, followed by SolB, and then SolC. As a result, SolC becomes the top (active) solution layer for the component.

If you later make changes to the component in SolA, those changes will not be reflected. The only way for the updates to take effect is to deploy SolC, since it is the top solution layer for that component.