---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Customizations Unchanged related list

# Customizations Unchanged related list {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Customizations Unchanged lists all records that were skipped (due to a customization),
but the changes that were going to be applied in this upgrade have not changed from the last
upgrade.

Navigate to System DiagnosticsUpgrade History to view the Customizations Unchanged related list.  
{#customizations-unchanged-related-list__table_b1j_fzg_sbb__entry__2}

| Field | Input Value |
|-|-|
| File name | Name of unchanged sys_upgrade_history_log record. Select it if you want to access [Upgrade Details](https://servicenow-prod.fluidtopics.net/xDRBo4NYXOETD2ywQ~lxYg "To prevent your customizations from being overwritten during system upgrades, the upgrade process skips (does not apply the update to) objects that have been customized. One of your responsibilities as the administrator is to resolve each skipped update after an upgrade.") and add comment text, or set a resolution status for it. |
| Disposition | Action performed on this file during the selected upgrade: * Inserted: The system inserted a new record. * Updated: The system updated this record. * Deleted: The system deleted this record. * Skipped: The system did not change this record in order to preserve customizations. * Reverted: This record was reverted to the base version. * Table not found: The system could not find the table that contains this record. * Unchanged: The system did not change this record because the baseline component has not changed since the last release. * Skipped Manual Merge: The system did not change this record because updating it requires manual intervention. * Skipped Apply Once: The system skipped this record because it had already applied an update from an xml file in the apply once folder. * Not Latest: The system applied a change, but this change was overwritten later during the same upgrade. {#customizations-unchanged-related-list__ul_c1j_fzg_sbb} |
| Priority | Relative importance of the conflict that caused the skip based on the following criteria: * 1 (highest priority): xml content * 2: script or script_plain * 3: html content * 4: sys_ui_form_section, sys_ui_related_list, or sys_choice_set * 5 (lowest priority): other {#customizations-unchanged-related-list__ul_d1j_fzg_sbb} |
| Resolution | * Reviewed * Retained * Reverted {#customizations-unchanged-related-list__ul_e1j_fzg_sbb} |
| Comment | During the process of resolving a skipped update, you have the option to add a Comment to any record. For example, the comment might explain the action that you took to future reviewers. |
| Changed by vendor | Indicates whether the file has been changed by the vendor since the last upgrade. |
| Target name | Name of the record corresponding to the current file. |
| Plugin | Plugin that contains the record. |
| Type | Current file type (such as Business Rule or UI Policy). |
| Table | Table that contains the record. |
[Table 1. Customizations Unchanged related list]

{#customizations-unchanged-related-list__table_b1j_fzg_sbb}
* **[Revert a customization](https://servicenow-prod.fluidtopics.net/mdrbG5mNRMXryJfhGu2hQw)**   
  To prevent customizations from being overwritten by system upgrades, the upgrade process automatically skips changes to objects that have been customized. You may want to overwrite your customizations when a software upgrade contains a feature that you would like to implement.

*[\>]: and then