---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Customer Updates table

# Customer Updates table {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Changes made in the system are recorded on the Customer Updates
`[sys_update_xml]` table chronologically. There are a few exceptions, as noted
below.
To navigate to this table, enter <kbd class="ph userinput">sys_update_xml.list</kbd> into the
navigation filter. For information about update sets, see [System update sets](https://www.servicenow.com/docs/access?context=system-update-sets&version=australia&pubname=australia-application-development&ft:locale=en-US).

The following information is stored about each update:  
{#r_CustomerUpdatesTable__table_u4z_gcl_sq__entry__2}

| Field | Description |
|-|-|
| Name | A name that identifies the updated record. |
| Created | The date and time the Customer Update record was created. |
| Created By | The user who performed the change. |
| Type | The type of the update. |
| Updated | The date and time the Customer Update record was updated. |
| Updated By | The user who performed the update. |
| Updates | The number of times the record has been updated. |
| Target Name | The name of the element that was altered. |
| View | The view of the form that was altered if it was a form layout change. |
| Payload | The XML contents of the record after the change. |
| Remote Update Set | A reference to that update set if the change was performed by a remote update set. |
| Local Update Set | The update set the change is associated with. |
[Tabelle : 1. Customer Updates table]

{#r_CustomerUpdatesTable__table_u4z_gcl_sq}  
Hinweis:  
Some application changes are not represented by Customer Update records (sys_update_xml) Examples:

* Types of metadata where updateSynch = false
* Cascading changes to tables and fields such as display name changes
* Unresolved metadata references from other applications (resulting in no "display value" on the element)
* sys_id changes for coalescing files
* Changes to Flow/Flow Actions that may generate sys_documentation
* ua_table_license_config records generated on table creation
* Jobs running in the background such as natural language processing
* Cases where sys_update_xml is manually modified or removed

{#r_CustomerUpdatesTable__ul_zwf_txr_spb}

To learn more, see Commit changes.