Power Platform Community Forum Thread Details

Dear reader,
using both pipelines as manual transport, I'm facing a dead lock situation at my clients'.

Solution A is deployed from Dev to Test to QA. But when deploying to Production, it fails stating:

Failed to upgrade solution. Solution dependencies exist, cannot uninstall. DependencyCount : 1 RequiredComponentObject details: Type: Role, ObjectName: _Business Ontwikkelaar Warmte Infra, Id: 64d13f1b-3557-ec11-8f8f-0022489b868b, ParentObjectName: , ParentId: 00000000-0000-0000-0000-000000000000, DependentComponentObject details: Type: AppModuleRoles, ObjectName: , Id: b8fd89ec-cf32-4fee-844d-9e503281dd13, ParentObjectName: , ParentId: 00000000-0000-0000-0000-000000000000

leaving me with an A solution and an A_Upgrade solution in production.

I can't Apply Upgrade on A, it will return the above message.

I can't delete the A_Upgrade solution (hoping the entire process would be reverted) because of already existing dependencies (I covered up the solution name to make things less complicated):

I tried to deploy an entirely new version from Dev to T, QA and Production. All went well until production told me that 3 dependencies where left.

I can't delete the role from the first error message, for an MD App seems to be depending on it:

Ofcourse I took the App apart (which, by the way, is exactly the same in Dev, T and QA without unmanaged layers), it isn't shared with this particular role and it isn't set in the App definition as one of the roles that should be able to access it.

I'm kind of "at the end of my Latin" (directly translated from a Dutch saying), I'm lost.

Any bright ideas?

Thanks for thinking along with me.
Regards!
Jeroen

Categories:

Microsoft Dataverse with Power Apps