After clone, test instance not showing recent changes that were committed

[BijoyDeb]

Hi All,

I just cloned our test instance from prod.
Before few days, I moved few updates sets from dev to test for users to do UAT on

But after the cloning, I can see those changes are not showing any more in test instance (changes were like catalog changes, dictionary changes etc)

Is it  usual scenario as I have done this for first time.

Do I need to commit those updates from dev to test again or is their any way that I would have taken care before clone?

[Anand Kumar P]

Hi @BijoyDeb ,

After clone test instance will become the blueprint of prod and your updatesets wiped out.

You can export your updateset again from dev to test and commit so you will see the customisations.

Before clone scheduling you have take backup of the updatesets.Else it will be wiped out that is how clone will work.

If my response helped, please mark it as the accepted solution ✅ and give a thumbs up👍.
Thanks,
Anand

[Robbie]

Hi @BijoyDeb,

The quick answer to your question, if you didn't change the deafult settings on the Clone request (specifically both the 'sys_update_set' table as well as the updates themselves 'sys_update_xml'), then unfortunately the update set table (along with a number of other key tables) will be overriden from the source instance - in your case Prod.

The quick fix for you would be to reapply the updates. This is not a bad thing as you can now test the updates sets against the latest copy of Prod.

Moving forward, this can however be easily changed.

When cloning back, there are a few key steps to consider - add tables to the 'Excluded tables' list which essentially ensures that these tables are not overriden ; )

See the screen shot below and also take a look at the best practices around Cloning back: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1214608

To help others (and for me to gain recognition for my efforts), please mark this response correct by clicking on Accept as Solution and/or Kudos.


Thanks, Robbie