Different sys IDs in DEV, TEST and PROD instances

[SwatiYeginati]

Hi SNOW Folks,

I am having issues when moving updates from dev to test and prod instances. We have created new security groups in Azure as per our needs however when the groups sync with ServiceNow, the sys ids generated are different across the three instances. Can you please suggest what is the best way for maintaining uniform sys ids across the instances?

Thanks,

Swati

[Michael Fry1 · Accepted solution]

You should only be syncing to one instance, ie Prod and then via Clone down or XML, move the records to other instances. XML will maintain the sysIds.

[Michael Fry1 · Accepted solution]

You should only be syncing to one instance, ie Prod and then via Clone down or XML, move the records to other instances. XML will maintain the sysIds.

[Steven Parker · Accepted solution]

Snycing should only be done in PROD and then I typically move the XML of the record from PROD to DEV to maintain the same sys_id between instances.  Cloning would also solve this, but below is the process I use when we create a new group.

So go to the group in the ServiceNow PROD instance, click the Hamburger icon, then Export, and XML (this record):

Then go to DEV and the groups table (the record knows where to go so the table isn't that relevant but I always go to the actual table the record belongs to)..Right click any of the column headers, then Import XML:

Then upload the XML file and the group will then appear in the DEV instance.  

You can then perform a group sync in DEV as long as the user sys_ids match between the instances.  Just remember DO NOT perform a USER sync in DEV, but you can import (or clone) users from PROD to DEV and then perform a GROUP sync in DEV to get the users into the correct groups.  I typically don't move users from PROD to DEV unless they are IT employees who may need to use DEV for testing or have tasks assigned directly to them.  We use Active Directory, but this logic should be the same for you I would think.