Powerapps No longer allows saving over another app.

[PowderTracksAdm]

Up until this most recent update of Powerapps, I used to be able to save an app over another one. It would show up under the overwritten app as a new version that can be published at will. Now, I can no longer do that. When you click on save (which has moved to the right side and doesn't function the same), it just gives you the option to save the current app and if you click on "Save a Copy" it only lets you put in a new name. If you try putting the name of the one you want to overwrite, it tells you "That app already exists". Well no kidding! That is what I want. I used the over writing ability to keep two versions of an app, a "Beta" version and a production version. This allowed me to have my test users use my "Beta" in a "live" environment without needing to overwrite the main app. I am aware, I could export the app then import, but this probably wouldn't allow me to over write either. Please, am I missing something? I have to get some new changes pushed out but it won't let me!

[Pstork1]

You are not missing anything.  Saving over an existing copy is no longer supported and really isn't necessary. If you want a beta copy of the app you should be building that in a different environment and then exporting importing it into the new environment. You can approximate what you are describing by Publishing the Beta and then restoring an old version if you need to roll back the changes.  

[PowderTracksAdm · Accepted solution]

Nevermind, I found a way to fix it. However, I will report this issue to Microsoft, because it is going to be a problem when they push out these changes. Here is how I fixed it:

1. While in the Editor, click on "Settings". 

2. Go to Upcoming features

3. Scroll down until you see a switch for "Enable Legacy Ribbon"

4. There you go, back to how it was. 

[PowderTracksAdm]

Thanks for the reply. I am not sure you are understanding what I am doing. I do have a Beta in a different environment. I have my main application, the "Production" version. This is the one everyone uses on the daily. I name it "Powder Tracks". I have a second app, entirely seperate from that one called "Powder Tracks Beta". I make all changes and new builds in this one, publishing and rolling back changes as needed. SInce both systems use the same data in the databases, my test users can use the "beta" and let me know how the new features will perform. When I get an all good from my testers. I will save and publish my current version to the "Beta". Then I would "Save as" and save over the main production, "Powder Tracks". This would create a new version in that one. Now all I would need to do is hold a "features" update meeting with everyone and let them know what day I will be rolling out the changes. The next morning, I make that new version live. Viola, Hello new production. Objectively, I found that "Save as" ability significantly easier and quicker than Exporting the app and importing it over the other one. 

[Pstork1]

Unfortunately, that uses a loophole in the system that MS has now plugged. Enabling the legacy toolbar will work for a while, but eventually that will go away and you'll be left with the same problem. The best way to do what you are describing is to build your app in a different environment using a Solution.  When you are ready to move it to production export the Solution and apply it to production as an update.

[Anonymous]

Hi @PowderTracksAdm ,

I know this post is marked as "Solved" but have a look at this post.

Hopefully they keep the functionality, it's just a little more hidden.