Clone Profile additional records

[JohnnySnow]

Hi Team,

We are in the process of cloning the prod instance to dev.

But before doing that we had to create a data preserver for few of the properties. We did create a new data preserver, however, there was no option to map that preserver to a clone profile. We were using the system profile which we later came to know that it is readonly by default.

Hence we created a new profile, but after saving we could see the exclusions were 169, preservers 132, clean up scripts 13.

When we compare this with default system profile it is exclusions 151, 113,11 respectively.

We are not sure what should we do with the additional records. Has someone faced similar issue while creating the clone profile? If yes what actions did you take ?

[James Chun]

Hi @JohnnySnow,

Yea, I had a similar issue a few years back, the total numbers of records in the related lists (exclusion, preservers, cleanup scripts) in the Clone profile don't add up. 

If you open your custom profile and its related lists, you will see that they are from not just your profile but include the entities from the System Profile as well. This is very misleading as you assume it should only contain the ones associated with the selected profile.

If you have created your own entities and want to incorporate them into the clone, please refer to the documentation here - https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0855777

Worst case, you can roll back and do it again (which I did a few years ago) but better to get it right in the first go 🙂

Cheers

[Sumanth16]

Hi @JohnnySnow ,

Please refer to below thread:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0855777

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0851927

If I could help you with your Query then, please hit the Thumb Icon and mark it as Correct !!

Thanks & Regards,

Sumanth Meda

[JohnnySnow · Accepted solution]

Update: We didn't do anything to the list of new records, that didn't seem to cause any issues and the clone was successful. In our case, the exclusion tables didn't have any records so we were good.

But I would suggest you guys to check the your tables & data preservers before proceeding.