idea Revert to published app config / Delete draft config in ArcGIS Experience Builder Ideas

Revert to published app config / Delete draft config

DeanMoiler — Tue, 20 Feb 2024 16:39:12 GMT

I've come across an issue in which the configuration of my app is broken (through using functionality of the ExB GUI only), though the published version works just fine.

Even without such issues, it would be really useful to be able to revert to the published version / delete the draft of the app, as you can do in Sites, to start again from the published version:

Re: Revert to published app config / Delete draft config

MarthaRodgers — Fri, 07 Jun 2024 00:19:53 GMT

Yes, this would be very helpful! And honestly, why even give me an option of Save vs. Publish if I can't go back to the Published version? I mean it's nice to have, as a temporary view, but very frustrating when you can't delete "the draft" version.

Re: Revert to published app config / Delete draft config

DanMakridakis — Mon, 01 Jul 2024 19:12:37 GMT

Hey Dean,

I just posted a similar idea that would also include this functionality. Check it out:

https://community.esri.com/t5/arcgis-experience-builder-ideas/virtual-draft-states-for-enhanced-version-control/idi-p/1499983

Re: Revert to published app config / Delete draft config

K_Jueckstock — Mon, 23 Dec 2024 18:18:37 GMT

I also am in need of this functionality, would be super helpful as we have multiple editors in a web experience and I've now lost quite a few of my original edits and am unable to get them back, despite them showing up fine on the published site

Re: Revert to published app config / Delete draft config

OpenDataCLE — Tue, 04 Feb 2025 13:06:32 GMT

ESRI, please consider this. You built this incredibly customized app builder, but it's hard to do any long-term development with teams without a bare minimum of version control. At the very least why shouldn't there be a way to revert to the published version?

This is something I hope takes months, not years to add. Saving multiple copies of an already published Experience is unfortunately not a useful option when our whole organization is already referencing the published authoritative version.

Re: Revert to published app config / Delete draft config

JPrüssmann — Thu, 06 Feb 2025 16:24:19 GMT

I had my experience all finished for larger views, and was working perfectly. I published it a couple of days ago, and today I did the optimization for the smaller screens, by changing from the default to custom structures for each of my pages and moving things around so that they would fit better. I though that by doing this, the changes I made would be reflected only in the tablet and phone views of my experience. After doing all that work, I went then back to the larger screen size view, and oh surprise, things had moved around there too, in a very bad way.

Now I need to revert the changes I made and go back to the version I last published to my experience. So, please please esri, please implement this idea, it'd be much appreciated. Thanks!

Re: Revert to published app config / Delete draft config

jessneuner — Fri, 28 Feb 2025 19:00:41 GMT

Excellent idea!

Re: Revert to published app config / Delete draft config

LLeighfield — Mon, 07 Apr 2025 20:35:37 GMT

This is a no-brainer! We've just run into a similar situation and a discard should have been part of the initial product release.

Re: Revert to published app config / Delete draft config

CassNEGIS — Thu, 24 Apr 2025 14:57:27 GMT

I would like to second the idea to have a "revert to published/delete draft" option in ExB.

Re: Revert to published app config / Delete draft config

AdamBargar_PUCO — Wed, 04 Jun 2025 14:31:31 GMT

I agree with everyone here. Kinda can't believe we have to ask for this lol. Should have been an option from the start.

Re: Revert to published app config / Delete draft config

IsakL — Fri, 28 Nov 2025 15:02:36 GMT

With knowledge of the APIs / ArcGIS Assistant this is fairly easy to do yourself. Which makes it even more baffling that this is not simply available as a graphical option.

For those unaware, here's how to do it:

Open your experience in ArcGIS Assistant, click View Item JSON and go to the Data tab.
Copy all contents and paste this into Notepad or a similar text editor on your own PC, then save the file with the file name config.json
Go to the Resources tab in ArcGIS Assistant. Click on Upload file, under Optional folder name enter config, then select your config.json file. When asked if you want to replace the existing file, do so.

Note that when you click on config.json under the Resources tab you will be taken to a text editor. Do NOT use this - when editing resource files it is broken and will likely mess up your formatting, arcade scripts etc. Uploading the config.json file directly is the only method that works properly.