Unable to remove of managed solution

(0) Share

Report

Posted on by Michael Megel

I'm not able to remove a solution from PowerApps environment. I get this error message:

I have tried to analyse the dependencies and got:

So I tried to remove the Flow - but this is not possible because it is grayed out:

Than I tried to solve the problem by removing all connection references from Flow - it's now empty:

However, my solution have still this reference:

and deleting the flow fails also because:

What can I do?

Categories:

Governance & administering

All responses (5)

Answers (1)

Sort by

EricRegnier 8,720 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @megel, you'll need to determine what managed solution uses that flow and uninstall that solution which will remove the flow and the dependencies to your other solution. Cheers
Michael Megel 7 on at

Like
a
(0)

Report
Copy link

Link copied!

There is no other solution, which uses this flow 😥 in this environment. However, the flow never worked correct, because the Solution Import disconnected the flow from my PowerApp (CanvasApp) as well. I was also never able to import this flow in another PowerApp.

The only possible part can be the "doubled" PowerApp:
everything else is older than 1 month.
The PowerApps have also no more any connections or flows:

And I also can not remove any of this 2 PowerApps 😞
EricRegnier 8,720 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Weird, from your other screenshot below, it looks like the flow is part of a managed solution. In make.powerapps.com, navigate to solutions, then pick "All": , try to search in this list?
Michael Megel 7 on at

Like
a
(0)

Report
Copy link

Link copied!

No, I have removed all unnecessary solutions. There is no other solution, which contains this connector. But why is there this parent-id in the error message:

ccppi_sharedoffice365_7c14f, Id: 1109418e-09cb-4bf0-abc8-2d45ed32dfce, ParentObjectName: , ParentId: 00000000-0000-0000-0000-000000000000, DependentComponentObject details: Type: Workflow, O
Verified answer

EricRegnier 8,720 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Could be a bug with dependencies calculation... Suggest to submit a Microsoft support ticket at: https://admin.powerplatform.microsoft.com/support