Please answer my query

Deepa12
Tera Contributor

Hi,

 

i want to understand that Dev and production environment local update sys id should be same.

 

I migrated the local update set xml file from dev to prod. both having same retrieved sys id but update set sys id is differ.

 

pls advise me.

 

Update set

update set name

DEV local update set sys id

xxxxxxxxxxxxxx

PROD retrieved update set remote sys id

yyyyyyyyyyyyyyyyyyyyyyyyyyyy

XML file sys id

ssssssssssss(Same sys id in dev and prod)

PROD retrieved update set sys id

ssssssssssss(same sysid in dev and prod)

8 REPLIES 8

Roja Puppala
ServiceNow Employee
ServiceNow Employee

Am not sure why am i receiving these messages.

Kurian Thomas P
ServiceNow Employee
ServiceNow Employee

Hello @Deepa12 ,

1. Since prod does not have that update-set, it is a new entry in the local update-set table.
every new insert will create a new sys_id. So prod and dev will have different sys_id for local update-set record

2. xml file will show the sys_id in the current env (in your case local update-set sys_id in dev)

3. remote sys_id field in Retrieved update sets shows the sys_id of the record in the previous env ( in your case local update-set sys_id in dev)

4. So dev xml update-set value = prod retrieved update set remote sys id

I hope this helps 😄 mark it Thumbs up if you found this helpful

Johns_MP
Giga Guru

Hi @Deepa12 ,
i think it's an expected behaviour. The sys ids for the update set and retrieved update set and also the committed update set changes from instance to instance (because in the Prod instance it's kind of inserting a new record). However the changes that you have made/captured in the update set remains the same and once you commit the update set the changes you have made in dev will be reflected in the Prod.
One thing you can check is that go to the Retrieved update set and bring the Field Remote sys ID in list view, it should have the same sys_id as the dev update set.

Regards,
Johns M P

Ramamoorthy N1
Tera Contributor

Hi

When you export an update_set from source instance it randomly assigns a sys_id that will be assigned to the update_set post retrieved in the target instance - so why you see the sys_id of exported XML file and the update_set in the target instance are same.

Pls note the actual sys_id of update_set from source instance is not used to create the XML file when exporting.