Can we Disable csdm.lifecycle.sync.between.ci.and.asset.activated after clicking on Enable Life Cycle Sync on the Life Cycle Mapping table for Pre-Xanadu Behavior?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: ; } } Per the documentation https://www.servicenow.com/docs/bundle/yokohama-servicenow-platform/page/product/configuration-management/concept/csdm-life-cycle-standard-values.htmlthe system property csdm.lifecycle.sync.between.ci.and.asset.activated enforces synchronization between the life cycle states of Configuration Items (CIs) and their associated Assets. This synchronization primarily impacts CIs that are linked to assets. Disabling this property allows the life cycle migration process to include logical CIs that do not have asset associations, thereby aligning behavior with pre-Xanadu CSDM implementations. Additionally, when this property is enabled, legacy CI status values do not transition correctly to the CSDM life cycle stages, which may disrupt expected migration behavior. Request: Can this property (csdm.lifecycle.sync.between.ci.and.asset.activated) be disabled after clicking on Enable Life Cycle Sync on the Life Cycle Mapping table, in order to preserve pre-Xanadu behavior as requested by certain customers? 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: ; } } All Releases 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: ; } } The csdm.lifecycle.sync.between.ci.and.asset.activated property (Also called as function isProductInstanceSyncActive from LifeCycleUtil Script include) enforces synchronization between the lifecycle states of Configuration Items (CIs) and their associated Assets. It primarily affects CIs that are linked to assets. Disabling this property allows the lifecycle migration process to include logical CIs that do not have asset associations - essentially aligning behavior with pre-Xanadu CSDM implementations. A few technical notes: The bulk update job does not include the check for this property in its condition: This means bulk migration still utilizes all mappings to help populate the CMDB with lifecycle data. However, going forward, post bulk migration it won't attempt to sync non-asset CIs if the csdm.lifecycle.sync.between.ci.and.asset.activated property is set to true. To summarize:- It's not mandatory for csdm.lifecycle.sync.between.ci.and.asset.activated to be set to true. That said, disabling it reintroduces known drawbacks from the pre-Xanadu sync model - such as value flipping due to certain update actions. - Unless you're leveraging product instance-related activities that benefit from syncing the three class types based on lifecycle values, it's generally not recommended to set the property to false.