Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
The sys_id of a specific user's sys_user record is not the same between Production and sub-Production after clone - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • The sys_id of a specific user's sys_user record is not the same between Production and sub-Production after clone
KB0746228

The sys_id of a specific user's sys_user record is not the same between Production and sub-Production after clone


1775 Views Last updated : Sep 21, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms

  • After cloning, some sys_user record's sys_ids are different between Dev and Production. Due to that, some group memberships are having issues.

Release

  • London Patch 4, Hot Fix 2

Cause

The user has a Data Preserver for the sys_user table on their sub-Production (Dev) instance. This will prohibit a clone from Production down to this sub-Production environment from syncing the sys_ids in question.

Resolution

In this case, a sys_user record for one specific user was provided on each instance mentioned, both Production and sub-Production.

On Production, Bucky Barnes' sys_user record has a creation date of 2/23/2016. In the sub-Production instance, his sys_user record has a creation date of 10/15/2015.

The reason these are different, and the reason these have not been "corrected" or "synced" via a clone from Production down to Dev is that the user has Data Preservers set up on their Dev instance.

What this does, as covered in documentation ( ref: Data preservation on cloning target instances ), is protect data on the target instance from being overwritten (When cloning, the "Source" is Production and the "Target" is Dev).

This is why the values are not synced, hence the issue with groups between the two instances.

To resolve this, the user can remove the Data Preserver in their sub-Production instance on sys_user to effectively "sync" the sys_ids during their next clone.

As a convenience, simply append the following to the affected instance to see any Data Preserver(s) on or related to sys_user:

  • /clone_data_preserver_list.do?sysparm_query=tableLIKEsys_user

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.