Import Update Set from XML not working

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-17-2015 02:39 PM
I am attempting to import an update set from an XML file.
Steps:
Update Sets > Retrieved Update Sets > Import Update Set from XML > Browse local file > Press Upload
The Upload button does nothing, it directs back to the Retrieved Update Sets page but there are no new update sets retrieved. I stored by date and searched by name and the update set did not load.
Note the XML Update Sets were created in Eureka and we are now running Fuji. Would that be related to the issue? How can I import this XML update set?
- 17,553 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-28-2017 12:08 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-28-2017 09:11 AM
Do a search on the name instead of update date as the xml file might have a different unload date. It should work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-21-2018 09:13 AM
Here's what I did:
I marked the update set "Complete" in Dev, and then right-clicked on "Export to XML" under my Related Links UI Action list. I saved that file to my desktop.
I opened my Test instance (for this test as I would normally use the update set process). I opened a list view (any list view) and right-clicked on the header of the list and chose "import XML" and then selected the file I had saved on my desktop. It imported the XML file and put it in my Loaded Update Sets section, ready for Preview.
I hope that helps,
Richelle

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-11-2018 03:34 AM
I know this is an old post, but for anyone else who may be searching, I spent an hour today wrestling with this same issue. It turned out the developer who exported the original XML did not name the XML file the same as the actual update set name, which is a standard we have in place, so I was looking for the wrong name in the retrieved update set list.
It wasn't until I looked in the XML file itself and noticed this line:
<remote_update_set display_value="DFCT0033800-u001v001">60446160db94ab007a93fb131d961921</remote_update_set>
I realized I was looking for the wrong name.