web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Export managed patch a...
Power Apps
Answered

Export managed patch and unmanaged patch consecutively makes new UI hangs

(0) ShareShare
ReportReport
Posted on by 3

Reproduction : 

- Clone Patch for a solution 

- Export the patch to a managed solution then unmanaged solution consecutively with the same version number

- the UI will hangs 

 

Workaround : 

- It works on classic UI

 

PS: 

This issue is found on AdvancedInADay lab in Exercise4 Task 1 , step 25.

 

I have the same question (0)
  • JisungHan Profile Picture
    Microsoft Employee on at

    Hello @pwinata ,

     

    I have tested the repro steps in my test lab but the both managed and unmanaged solutions exported successfully as below:

     

    image.png

     

    I exported it in the same version. Would you please perform the action after clearing browser cache?

  • pwinata Profile Picture
    3 on at

    Hi JisungHan, 

     

    Thanks for replying. 

    I tried your suggestion with clearing all the cache and also tried it in Incognito browser

    But the issue still the same. 

    Check the vid below.

  • JisungHan Profile Picture
    Microsoft Employee on at

    Hi @pwinata ,

     

    Thanks for your response. Does it work if you export the patch not consecutively? I mean, exporting patches separatedly.

    If this issue has a business impact, please raise a service ticket to MS support to investigate it further. The issue happens on a specific environment only I believe. Possibly, there would be some dependency issue.

  • Verified answer
    CU01081947-0 Profile Picture
    716 on at

    Hello @pwinata,

    I have also experienced something along the same lines.

    I will have a solution, let's call it version 1.0.0.0.

    If I wanted to export that as a managed solution the environment will automatically put it to 1.0.0.1.

    Now if I want to keep it as 1.0.0.0 when I change it and export, the environment hangs, as you mentioned.

    My workaround is export it as unmanaged with version 1.0.0.1 and then once it's exported I then export the solution with 1.0.0.1 and change it back to 1.0.0.0 as a managed solution and it allows me to do it. Strange. 

     

    I raised a ticket with Microsoft and the support engineer was excellent. He said the product team will include a checkbox to let us choose not to increment if we so wish. So hopefully that will come soon. 

     

    Thanks,

    Garry

  • Joel CustomerEffective Profile Picture
    3,224 on at

    Have you considered using the build tools? It will export unmanaged to devops and move managed

    https://docs.microsoft.com/en-us/power-platform/alm/devops-build-tools

  • CU01081947-0 Profile Picture
    716 on at

    Hello @jlindstrom,

    Thanks for the reply. Lots of people say we should use them, but we don't. They are a little above my technical skills unfortunately.

    Thanks very much,

    Garry

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Vish WR Profile Picture

Vish WR 839

#2
Valantis Profile Picture

Valantis 533

#3
Haque Profile Picture

Haque 412

Last 30 days Overall leaderboard