Invalid connections inside solution workflows after importing a managed solution package

Hello folks,

I have had this daunting problem for a while now with a client. I have an unmanaged package in my own tenant where the development happens (Power Apps, Flows, Dataverse tables, custom security role) and when the client's solution requires an update, I'm pushing a managed package (zip-file) to their tenant using the "Upgrade" -option when importing the package. Just as a point, this target environment is located in another tenant and they are using the "(default)" -environment. I don't know if that helps.

Lately, after updating the app successfully, some of the workflows are turned off. When trying to turn these Flows on from the solution, I'm getting the following error which says I'm missing some connection references even though I'm not. All the flows in the target environment are using the connection references listed in the solution.

When I open the turned off -Flow in the target environment, I see that there are 2 invalid SharePoint connections:

In my source org, the connection is correctly configured to use the connection reference in the solution as seen below:

After I "fix" the connection in the target environment, save the flow and turn it back on, it creates an unmanaged layer in the component.

Some have suggested removing this unmanaged layer and that's what we have done, but that turns off the Flow and the connection issue is there again. There is no way I could turn on the Flow without creating an unmanaged layer.

Stuck with this. Any help from the community experts?

Thanks,

Ville

Categories:

Environment

Management

Quick Links

Leaderboard > Power Apps