Update set sys_id is different in every instance

[tushar_ghadage]

Hi All , 

I am facing some weird issue here  I have created the update set and captured platform analytics updates in it.

But when I try moving it to sanity test instance and then to test instance... 

they have different sys_id everywhere in dev , s-test and in test instance.

how come this is possible and when ?

anything would help 

thanks !!

[Ankur Bawiskar]

@tushar_ghadage 

should not happen ideally

did you check the customer updates which got captured in that update set?

[tushar_ghadage]

Yes, I have 

Customer updates count is same 

but out of that I have checked one customer update which is related to list layout for this sys_id is different as well ...

But I am not sure how it's different 

for eg . I made a change in layout in dev for incident then i moved it to test how come the sys_id can be different..

[Vasantharajan N]

@tushar_ghadage - There is no issues having different sys_id for the update sets. Can you confirm the update set record(customer update) payload having the sys_id from the dev instance is there in the target instance, post you retrieve it.

[tushar_ghadage]

i checked it for one record in customer updates ...

in the payload sys_id is same ...