Problem from export large update set to xml file

[leandrobenatti]

Hello all,

I tried do export an one large Default Update Set with have 44.000 lines to xml file, but I have a problem.

The process are done succesfully, but the browser cannot open the window to download.

I tried do export a minor Update Set and I have successfully.

What can I do?

Thanks.

[Michael Ritchie]

I have run into this before as well.   Basically the display transaction quota is getting in the way of your export.   Just so you know when you click Export XML, in the background all the sys_update_xml files for the local update set are being duplicated as a remote update set and then afterwards a processor bundles them for a download.   Because of your large number of updates, this process is taking longer than the transaction quota allows.

Go to Remote Update sets and see if you have one with the same name as your local update set.   Verify that the number of updates is the same number as your local update set.   If all is good, then the solution is easy:

1. First get the SysID of the remote update set.

2. Then append that SysID and your instance name into the following URL and launch it:

https://INSTANCE-NAME.service-now.com/export_update_set.do?sysparm_sys_id=REMOTE-UPDATESET-SYSID&sys...

If the remote update set is not available let me know and I can provide another solution basically emulating the Export XML script.

[puneetgoels1]

I tried it but it is downloading a blank update set with no customer updates

[moserism]

It does the same for me as well.

[LorenzVdV]

Worked for me for an update set with +13000 updates. I did have to use Troy's script below first because the Export to XML only got me 8000 updates in the copied update set.

Thanks!