CSDM life cycle mappings not syncing after activating Product Instance 2.0Issue <!-- /*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: ; } } According to ServiceNow documentation, once CSDM Life Cycle Mappings are turned on, synchronisation between legacy fields and life cycle fields occurs automatically based on mappings defined in the life_cycle_mapping table. However, after turning on the mappings and running synchronisation, the Life Cycle fields do not sync with the legacy fields. This behaviour is a result of architectural changes introduced in the Xanadu release with the Product Instance 2.0 (PI 2.0) lifecycle synchronisation model. Facts<!-- /*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: ; } } Release: Product Instance 2.0 (PI 2.0) and above Affected table: `life_cycle_mapping` Relevant system property: `csdm.lifecycle.sync.between.ci.and.asset.activated` Affected release: Xanadu and later 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: ; } } Product Instance 2.0 (PI 2.0) & Above 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: ; } } A. PI 2.0 is turned on (Xanadu and later) When PI 2.0 is turned on, all legacy sync occurs from the Asset record on the asset lifecycle fields (hardware_status / hardware_substatus) on CIs inherited from `cmdb_ci_hardware`. Fields such as operational_status are not included in this sync. With the Product Instance–based lifecycle synchronisation model introduced in the Xanadu release, ServiceNow changed how lifecycle data is managed across Configuration Items (CIs), Assets, and Install Base Items. Under this model: Lifecycle alignment is driven through Product Instance relationships. Direct synchronisation between CMDB lifecycle fields and legacy CMDB status fields (such as install_status and operational_status) is intentionally disabled. This design prevents circular updates and conflicting lifecycle values, particularly where Assets and CIs previously overwrote each other due to mismatched choice values and non-1:1 mappings. As a result: Non-asset CIs (such as Business Applications) do not sync lifecycle values back to legacy CMDB status fields once the new lifecycle model is turned on. Lifecycle synchronisation depends on whether a CI has a related Asset and participates in the Product Instance model. This behaviour is governed by the system property csdm.lifecycle.sync.between.ci.and.asset.activated. When set to `true`: The new Product Instance lifecycle model is active. CMDB records without a related Asset do not continue syncing legacy CMDB status fields after the initial bulk migration. When set to `false`: - CMDB lifecycle fields sync directly with legacy status fields. The instance follows the legacy CSDM lifecycle synchronisation. This option does not align with post-Xanadu CSDM implementations. B. PI 2.0 cannot be disabled It is not possible to disable Product Instance 2.0 (PI 2.0) or revert the configuration to the behaviour seen in Xanadu and earlier versions. PI 2.0 is the current standard approach. C. PI 2.0 is NOT turned on If PI 2.0 is not turned on, the system attempts to sync in multiple directions across as many lifecycle fields as possible, which causes inconsistencies.