How does CI to Asset synchronization work in ServiceNow, and which specific CI fields trigger updates for which asset types?Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Most users get confused between install_status and hardware_status — This article will help you to clarify which field drives the sync for hardware assets (alm_hardware) versus non-hardware assets like software licenses (alm_license) and consumables (alm_consumable), and which mapping tables (alm_asset_ci_field_mapping, alm_asset_ci_state_mapping, alm_hardware_state_mapping) are involved in each case. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Any Release Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Review the below script include,AssetAndCISynchronizer: /sys_script_include.do?sys_id=9ec37b411b012000e49bfbcd2c071380 Mapping tables included for sync: ASSET_CI_FIELD_MAPPING_TABLE: 'alm_asset_ci_field_mapping', ASSET_BASE_CI_STATE_MAPPING_TABLE: 'alm_asset_ci_state_mapping', ASSET_HARDWARE_CI_STATE_MAPPING_TABLE: 'alm_hardware_state_mapping', So the sync will consider different fields of CI's to sync the asset,Let's say you have a CI with an asset (alm_hardware). Now, if you change the install status of the CI, it will not update the Asset record.You have to update the hardware status of the CI, and it uses the mappings from the alm_hardware_state_mapping table and will sync the Assets1. alm_asset_ci_field_mapping — Field-level sync Handles general field mapping between CI and Asset records (e.g., name, serial number, etc.) for all asset types. 2. alm_asset_ci_state_mapping — Base/Non-hardware Asset state syncControls state synchronization for non-hardware assets, such as: [-]Software licenses (alm_license) [-]Consumables (alm_consumable) [-]Other non-hardware asset types [-]The field it watches is install_status on the CI side, and maps it to the asset_tag / substatus on the Asset. 3. alm_hardware_state_mapping — Hardware Asset state syncControls state synchronization specifically for hardware assets (alm_hardware), such as: [-]Servers, computers, network gear, etc. [-]The key distinction here is that it watches the hardware_status field on the CI, NOT install_status.