nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Revert to published version of Experience Builder (cancel changes)

JulieMikolajczyk

We were modifying a published Experience Builder application and we are now receiving an error "404: Resource does not exist or is inaccessible."

The published version works fine. While it would be nice to know what caused the error, the immediate need we have is to revert back to the published version and discard all unpublished changes. How can we accomplish this?

Find more posts tagged with

ArcGIS Enterprise

Accepted answers

All comments

RhettZufelt

If you are lucky enough to have not closed the experience yet, the undo button still works after a save/publish.

If still open, you can undo the changes, save, re-publish.

JulieMikolajczyk

Thanks so much, but I'm afraid we are definitely not that lucky! We saved and closed already.

TonghuiMing

@JulieMikolajczyk Yes, unfortunately, what @RhettZufelt mentioned above would be the solution. If the app has been saved, then for now there is nothing you can do to revert it back.

For similar cases, be careful with the Save function since it WILL update your app config. I would say the silver lining here would be, to use the Save as function more often, if there are multiple branches or versions, or from multiple editors:

rachelm

This just happened to us. The question is, what caused this to happen? Some weird blip of Esri's server?

BrittanyBurson

Wish we could revert changes after leaving the session. This was scary to go in and make and publish a new update today, with another surprise unpublished update along for the ride.

DeanMoiler

I've published an idea to add this to the ExB app, like it is in Sites:

Revert to published app config / Delete draft conf... - Esri Community

KoenVermeer_HE

There is a workaround to fix this if you have access to ArcGIS Assistant or some other means to read/ write the source json of the experience through the RestApi or Python.

The published version is saved in the json data
The draft is saved in the resource config/config.json

Copy the json from data, and save it to the config/config.json resource. Your draft will be reset to the published version.

NathanKoski

This works great, except be aware that it seems to undo any arcade code that you might be using to enrich text, so be sure to save a copy of your code separately before doing this.

MarkGo

I was messing around with an experience and migrated the configuration via ArcGIS Assistant from a branched version, which left me with a mismatch between published and the "draft".
This worked perfectly to revert the draft to the published version. Thanks!

rmcooper_wcpss

Thanks for this tip. It really helped me out after we implemented a change to our Portal URL.

I am curious: where on the Portal server is the config/config.json file?

I would have thought it was in the actual directory for the item in the contents directory: portal/usr/arcgisportal/content/items/{{item ID}}/resources/config/config.json

However, I believe this is only the config for the published version. I've looked high and low and cannot find where config.json used by the builder application lives. I'm glad the ArcGIS Assistant exists and can be used to access this file though!

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.