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.

[Shuvaday1]

I am bit confused which sysid to use.Is it the sysid of the updateset we are working on?I tried doing the same in the url provided,but it didnot give any result.Please help.

[Troy Riblett]

To add to Michael's answer above, it looks like there are some cases where if the update is big enough that the export to XML won't correctly copy the records (i.e. the number of updates in the remote update set will be less than the number of updates in the original)

So, one thing to try instead of using the "export to xml" button is to run the same script in the background instead.

In Scripts - Background

var updateSetExport = new UpdateSetExport();
var updateGR = new GlideRecord("sys_update_set");
updateGR.get("SYS ID OF UPDATE SET HERE");
updateSetExport.exportUpdateSet(updateGR);

[Shuvaday1]

Hi

I ran the script and it executed successfully.But how to download the updateset as xml?

[User367757]

I was working with 10.7k of updates, being asked to convert from source control integration back to Update Sets. (it happens) The export processor just did not want to do this.

Luckily I recalled that I could export any old XML, so just export the sys_remote_update_set and then all the sys_update_xml records and move them over to the target.

Sure, one XML would be great, but at least this works.

Thanks for the UpdateSetExport() script above. I recommend running it as Fix Script in the actual background so that it has leisure to complete.

[Abraham2]

In the above script is it the sys id of the local update set or the remote one? What is the reason for SN to copy the local to remote before exporting to XML? I have a similar issue..