Post Clone some of the users Sys_id is varying from production to Dev
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2022 10:30 AM
Hi
recently we did cloning, post clone we noticed that some of the users sys_id is different from production to dev.
but before clone, it was same sys_id.
what is the issue? how to fix this issue.
THanks.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2022 01:16 PM
Hi Deepa,
Can you share some screenshot for reference? Which module are you referring to?
Regards,
Deepankar Mathur
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2022 08:51 PM
Hi Deepa,
This is a common issue most face when integrating and bringing in users and groups and such. Most likely, a clone from Prod to your sub-prod instances will sync everything up if you bring your groups and users and such along with that clone.
Azure sync could be turned off for those sub-prod instances and either clones or export from Prod down could help keep those in sync.
So circling back, to answer your question, it is possible to have the same sys_id to the records already created by scheduling a clone from Prod to all your sub-prod.
Its' better to preserve data since user table has many types of users e.g service accounts, integration users, mid server users etc
Mentioned in this Post.
Mark my answer correct & Helpful, if Applicable.
Thanks,
Sandeep
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2022 06:50 PM
Hi Deepa,
Any update to this ?Any follow-up required? if not
Kindly mark the answer as Correct & Helpful both such that others can get help.
Thanks,
Sandeep