about update set

yuchen zhang
Tera Contributor

Hello,
I have two instances, but they are not dev and product, so the sys id of the data in them should be different, now I want to use an update set to move the updates from one instance to the other instance, but I want the sys id of the update set to be different after moving to the other instance, is it possible?

5 REPLIES 5

Suyog Aptikar
Giga Guru

Hi,

How are you trying to move code, I assume it would be via update source.

sys id would be different in both environments for update sets, however there is a field/attribute 'remote_sys_id' which should hold sys_id value of dev.

What is the value of sys_id say in dev and production when you move code now, can you share details as an example here to understand issue better.

If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.



Best regards

Suyog

Vijay Balotia1
Tera Guru

Hi Yuchen,

 

By default is not possible because each will have there unique ID therefore you cannot make the same sys_id. but you can try the below workaround.

 

1. Move  your update in one instance.

2.  You can make batch update set which include both instances update set therefore it will keep only latest update.

3. or else you can merge both the update set.

 

recommendation is go with batch update set and then move batch update set on your higher instance.

 

Thanks,

Vijay Balotia

Please mark the appropriate response as correct answer and helpful, This may help other community users to follow correct solution.
Thanks
Vijay Balotia

Astik Thombare
Tera Sage

Hi @yuchen zhang ,

To Change sys_id of the update set please follow following steps :

 

  1. Create a New Update Set in the Source Instance:

    • In your source instance, create a new Update Set and make all the desired changes within this Update Set. Ensure that all your changes are captured within this Update Set.
  2. Export the Update Set from the Source Instance:

    • Export the Update Set from the source instance. To do this, navigate to the "Update Sets" module, open the Update Set, and use the "Export to XML" option. Save the exported XML file to your local machine.
  3. Modify the XML File (Optional):

    • If you want to change the sys_id, you can open the exported XML file in a text editor and manually edit the sys_id value. However, please be cautious when doing this, as it involves modifying the XML structure.
  4. Import the Update Set into the Target Instance:

    • In your target instance, navigate to the "Update Sets" module and use the "Import Update Set from XML" option. Select the modified XML file you exported from the source instance.
  5. Review and Commit the Update Set:

    • Once the Update Set is imported, you can review its contents to ensure that all changes have been correctly captured. Make any necessary adjustments if needed.
    • Finally, commit the Update Set to apply the changes to your target instance.

Please note that manually modifying the sys_id of an Update Set is not a typical practice, and it should be done with caution. Changing sys_ids in this way can lead to potential issues if not done correctly. It's essential to thoroughly test the changes in your target instance to ensure that everything works as expected.

Additionally, remember to follow your organization's best practices and consider involving your ServiceNow administrator or a developer who is experienced with ServiceNow to ensure a smooth process.

 

If my ans helps you .Please mark it as correct 

 

Thanks & Regards,

Astik Thombare

Hi @yuchen zhang ,

 

Please,mark my answer as correct if it helps you.

 

Regards,

Astik Thombare