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 !!

[Renat Akhmedov]

Hi @tushar_ghadage,

This behavior is expected when working with Platform Analytics artifacts. The objects "Indicators",  "Indicator Sources",  "Breakdowns",  "Breakdown Sources", and "Dashboards" are created using dynamic sys_id generation during import.

ServiceNow intentionally re-creates these records on the target instance with new sys_ids, even if they came from an update set.

This happens because PA content is tied to background tables and dependencies that do not support strict sys_id preservation the same way standard configuration items do.

So seeing different sys_ids in dev, s-test, and test is normal.

Even though sys_ids differ, the functional links remain intact because ServiceNow rebuilds all references when importing PA definitions. This should not break dashboards, widgets, or indicator relationships.

If my answer was helpful, please don’t hesitate to give it a thumbs-up - it only takes a second, but it means a lot to me. Thank you!

Best regards,
Renat Akhmedov