schedule job doesn't save in update set

[Goran WitchDoc]

I'm wondering if anyone else having a problem with schedule jobs doesn't save in update sets. How do you move update sets between instance in a good structured way and together with the update sets that you want the scheduled job to be in?

[anupama8]

Hi Goran,

Update set do not capture the schedule job. This is the OOB functionality and this is how it functions.

Alternative way is create a script Include and then call it in schedule job. Script include will get captured in update set. So that in future if you need to make any changes in the code you can do it in script include and capture and move it through update set and there will be no need to make a change in schedule job. For the first time, yes, you have to move the schedule job manually (import and export xml).

PS: Hit answered, like, Helpful or Correct depending on the impact of the response.

[Deepak Ingale1 · Accepted solution]

Hi Goran,

Scheduled jobs, User accounts, incidents are considered by ServiceNow as "Data Records". Hence, these records are not captured in update set.

There is an architecture in a design of ServiceNow.

If you go to the "Dictionary" table (sys_dictionary"), you will see that some tables have "update_sync=true" attribute. Those tables who has this attribute present, only gets captured into update set.

There are different ways to transfer "Data records" like scheduled jobs. You can right click on the record and export it in XML format.

You can then import this XML format record into other instance. There are best practices involved in this approach though, like you should have "referenced records" present in XML file available on the target instance.

Exporting and Importing XML Files - ServiceNow Wiki

[Goran WitchDoc]

Typical. Was like I suspected. Guess I have to write it down in my release notes and do a XML.

Thanks for the confirmation.

//Göran

[Ashley]

If you try and force it into an update set you receive the error message:

This is very much not correct as it's not captured in the current update set and have to do an XML Export to keep all the instances up to date, not good practice.