The sys_id of the records are not matching between source and target environments post clone

[Dinesh_RS]

Hello Everyone!

The sys_id of the records is not matching between source and target

I would like to know if the sys id of the records in source and target would be same if we clone the instance.

Note : We have not defined a table under "Exclude Table" and "Preserve Data"

Clone results based on Exclusion and Preserver configuration - Support and Troubleshooting (servicen...

[Mark Manders]

Yes. A clone will be an exact copy of the source instance, including the sys_id's. You aren't sharing what records you are looking at, because by default there always be tables excluded/data preserved, even if you didn't define any yourself.

[HIROSHI SATOH]

The cloning process does not guarantee that the SysIDs will be the same. In particular, the SysIDs of roles added by plugins may be different.
It is a case-by-case basis, so you will need to identify the tables with differences and investigate the cause.

[Dinesh_RS]

Thank Mark & Hiroshi,

I missed to mention the table name. We have a custom table "x_nuvo_eam_user" and we haven't define this either in Exclusion list & data preservers. As far as I know, if we don't define the table in both exclusion & preserver list, then whatever the data in the source will only be copied to Target with the same sys id. (The data before the clone on the target will be removed)

Any suggestions on how we can find out why the sys id are different?

Thank you!!

[Mark Manders]

Create a ticket with NowSupport to see what happened. We don't have access to your instance, so we can only say that your statement is correct: the sys_id's should have been the same.