Exclude specific dataset from a table during cloning
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-16-2025 10:05 PM
I have set up a clone profile (derived from Out of Box System profile) wherein I have added an exclusion rule (Clone excludes) to prevent cloning regulatory records (decided by attributes) from a table using the following attributes-
- Table (not present on Clone excludes form)
- Conditions (not present on Clone excludes form)
I haven't seen usage of above mentioned attributes on any existing Clone exclude records so I would like to know if this setting will be able to accomplish cloning of those records from the table which don't satisfy the condition. I am aware that we can write post clone cleanup scripts to remove unwanted records from a table but if the configuration present on Clone excludes work then it will reduce the clone time.
I will give an example here. Only clone incidents which are not Priority 1 from production instance to sub-production instance.
Please let me know if anyone has tried this capability on Clone excludes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-17-2025 12:27 AM - edited ‎04-17-2025 12:28 AM
Hello @Kshitij Tripath ,
I have not tried it myself but heard from other admins that the "Condition" on Clone Exclude Tables is not being applied when cloning. The whole table will be excluded from the clone instead.
It seems to be a legacy field and it's also not mentioned in the documentation.
So yes, you would need to create a Post Clone script that deletes the undesired data.
Regards,
Robert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-17-2025 03:50 AM - edited ‎04-17-2025 03:53 AM
You can only exclude tables, not records. Simply because there is no 'conditions' field.
You can put conditions on data preservers, but that's related to the data already on the target instance.
For your use case, you could decide to exclude the incident table and preserve them as well, meaning no records from PROD will be copied to DEV and all records from DEV will be there after the clone.
Exclude = true, no Preservers
Will not copy any records, so no data will be on the target after the clone
Exclude = true, Preservers = true (can be with conditions on preserve)
Will not copy any records, but will put back the data from the target, based on the given conditions
no Excludes, no Preservers
Will copy all records from the source instance to the target instance
no Excludes, Preservers = true (can be with conditions)
Will copy all records from the target AND will put back the preserved records (could cause duplicate records, if the clone contains records you are also preserving)
Data filtration (I guess that's what you were talking about?) does not apply to cloning.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-17-2025 08:28 AM
Hi Mark,
Thank you for the response. I would like to highlight that there are Table and Conditions field in the Clone Exclude Tables dictionary. It is just that ServiceNow hasn't documented them. These fields are neither present on the form (platform view) by default nor they appear on Clone Admin console configuration.
I will raise a case with ServiceNow and let them confirm its functionality.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-01-2025 09:35 AM
Hi K**bleep**ij
We are also needing to exclude certain records from our security incident table from the clone, so I just wanted to ask if you had managed to get a solution yet? Thanks!