Clone Profile : Behavior of table Excludes/Preserve during CloneIssue On Orlando, after the clone is completed, the customers will notice the data in the tables added in excludes or preserves are not excluded or preserved.ReleaseOrlandoCauseThis is mainly because of the presence of "System Profile" in the Profile field. During the Orlando release, the clone profile was a part of an enhancement. By default, ServiceNow provides one profile called "System Profile" that will only include the OOB defined list of excluded tables, preserve data entries, and clean-up script. The Clone Profile has its own set of preservers/excludes. When the profile is selected then the clone profile automatically populates the clone request with your selected profile settings.ResolutionKeep the profile field empty while requesting a clone. Add the desired tables to exclude or preserve in the Clone Definition.If you wish to keep the "System Profile", then add the tables in the "Exclusions / Preservers" list in the Clone Profile. If you wish to proceed with this option, please note the existing PRB1399987/KB0851927 Unable to create Clone Profile Exclusions or Clone Profile Preservers for non-Global/scoped application tables. If you create a new profile, it won't let you add tables that were created in scoped/non-global app tables. Subscribe to the PRB to determine when the fix may be implemented. Related LinksClone profiles for clone requestsRequest a cloneClone results based on Exclusion and Preserver configuration