How to Preserve Service Portal branding when cloningIssue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } ul{ list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> Description To preserve the Service Portal branding when cloning from prod to sub prod instance, identify the tables and records to preserve, then create a data preservers on the source instance. Procedure Identify the table and records in the instance that need to be preserved. In this example a customer wants to preserve the text warning "PLEASE NOTE THAT THIS IS NOT PRODUCTION" that is coming from the "HTML Template" field in the widget record. Because this widget does not exist in the source instance, the sp_instance table needs to be preserved as well. If assistance is needed finding where a particular object is coming from, use the script below from the Chrome developer tools console, or create a task for CS-User Experience. // BEGIN SCRIPT $("div [widget='widget']").css("border", "1px solid red").css("padding-top", "20px").css("position", "relative").each(function(i){ var scope = $(this).scope(); var widget = scope.widget; var elem = $("<div style='position: absolute; top: 1px; left: 1px'><a target='_blank' href='/$sp.do?id=widget_editor&sys_id="+ widget.sys_id+"'> "+ widget.name +"</a> </div>"); var printScope = $("<a href='javascript:void(0);'>Print scope</a>").on('click', function(){ console.info(scope); }); elem.append(printScope); $(this).append(elem); }); // END SCRIPT This will outline all the widgets on the page and give you a clickable link to go to that widget. Example: Steps to create data preservers: Login to the target instanceFrom the filter navigator enter sp_widget.listFilter where Name = Not Production WarningAdd the Body HTML template column to your filtered view then notice the entry: PLEASE NOTE THAT THIS IS NOT PRODUCTIONConfirm that this entry is correct. Now, preserve the table and records on the source instance so the target settings will not be overwritten by clones. Login to the source instance.From System Clone > Preserve Data and create a new clone preserver: Name: Widget Theme: Check Table: Widget [sp_widget] Where Display Name = Not Production Warning Also create a data preserver for the sp_instance table if the widget does not exist in the source. The instance record is what ties the "Not Production Warning" widget to the actual container record that is on the Service Portal page. Login to the source instance.From System Clone > Preserve Data and create a new clone preserver: Name: Instance Theme: Check Table: Widget [sp_instance] Next, schedule a clone to test the data preserver.