Unanswered

Solution import, unmanaged layer prevents updates to both a Power App and Flow

(2) Share

Report

Posted on by westerdaled

672

I am experiencing a real headache when imported my solution from the Dev environment (unmanaged) into Production (managed).

A least one Power App and one flow won't update and in both cases they show the unmanaged layer in solution layers. To fix I have been removing the unmanaged layer as per various posts and discussion on this forum.

Firstly, what is it about these that means I have these unmanaged layers, haunting them given similar Power Apps and flows in the solution aren't showing the unmanaged layer? How do I ensure these are removed from the merging process or that their contents get move to the managed layer? if not can I automate removing the unmanaged layer?

Now, the real pain: in the case of the Power App , it calls a flow as well as having SharePoint data connections via environmental var . When I remove the unmanaged layer, the Power App looses the connection to the flow - great UAT experience 🙄 for my users. Again, to fix I as system/ environment admin, I have to edit the Power App in production and reconnect the flow 😯

The SharePoint data connections are fine.

Are there any tips or best practices to make this less excruciating ?

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (2)

Answers (0)

Sort by

westerdaled 672 on at

Like (1)

Report
Copy link

Link copied!

I wonder if this the answer.... ( since I don't how to transpose the two solution layers) .

Update: this should come with a health warning as it removes the unmanaged layers in some of the Apps and flows in the Production environment before applying updates. The result is the called Flows are no longer connected and need to be removed, and re-added sigh😫

Really the issue is down to the creation of the unmanaged layer in the when upgrading a managed solution in Production. The top layer (see below) wins and seems to regularly block the update happening during the import until I remove it and repeat the Solution import. There has to be a way to avoid this....

Call to Action: I would be interested to hear what other issues folks are having using the modern and classic solution import process. I do witness other Power Apps which don't seem to upgrade despite me chosing the "overwrite customisation optionm in classic. Making UAT quite torturous tbh😒

Update: I have now demonstrated this issue and another "showstopper" related to Solutions in our environment,to Microsoft who are looking into providing a fix for me.

Was this reply helpful? Yes No
HFG 524 on at

Like (1)

Report
Copy link

Link copied!

Hi @westerdaled

Did MS sort this out for you? I am seeing these unmanaged layers all over my flows imported into my test environment (Managed Solution) from my Dev environment (Unmanaged Solution). I was wondering if there was a way to avoid it happening? We're already having a nightmare with flows deactivating and connections being lost from one environment to another so I'm really hoping I don't have to go through each flow and delete this layer and reactivate at each deployment.

Thanks in advance for any insight you can share.

Was this reply helpful? Yes No