Rename Update Set Export File Name

I know I’ve lost an update set in the past after a clone. Not because I didn’t back it up. But because I couldn’t find it locally on my drive. Or I did but all the names were too much to keep straight.

There’s a bunch of ways to mitigate that loss. I’m not going to go into weather or not you should move everything up or what not. This post is just about making the “Export Update Set” button give you a file name that makes more sense.

You can update a OOB Script include ExportWithRelatedLists to change how it works for exporting update sets. There’s a function, getFileName that determines the name of the file. Normally it’s just table_sysid.xml. You can add an if and rename it. Here’s the code I’ve used to do this.

  getFileName: function(){
  // added customized name for exported update sets
              // script include: ExportWithRelatedLists
  var name = (this.parent_table + '_' + this.sys_id + '.xml');
  if(this.parent_table == "sys_remote_update_set"){
    var sus = new GlideRecord('sys_remote_update_set');
    if(sus.get(this.sys_id)){
        name = sus.getValue('name') + '.xml';
    }
  }
  return name;
  // end of addition
      // return (this.parent_table + '_' + this.sys_id + '.xml');
  },

Further Reading: Community Post

unsplash-logoZoltan Tasi

Avatar
Jace Benson
ServiceNow Developer

ServiceNow is my day job, JAMStack is my passion.

comments powered by Disqus