Azure Service Graph Connector
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hi All,
Azure SGC- updates the install status but not the two life cycle fields.
For few class like server, linux connector is updating life cycle fields but it does not update for classes like cloud network, cloud resource etc. I also tried creating new lifecycle mapping on cloud resource but it does not updates life cycle stage and status. (Reverse sync choice is true)
Can someonce please help me understand here why this fields are not getting synchronize through the azure connector.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
53m ago
Hi @shrutimkada,
Please check out the following KB Article: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2477752
Sharing its content below:
Issue
The Life Cycle Stage and Life Cycle Status fields are not updating for Non-asset Configuration Items (CIs) in Xanadu and later versions of ServiceNow. This issue arises because the synchronization mechanism primarily targets CIs linked to assets, leaving non-asset CIs out of the update loop.
Release
This issue affects all releases of ServiceNow from Xanadu onwards.
Cause
The root cause is the system property "Product Instance Sync (csdm.lifecycle.sync.between.ci.and.asset.activated)" being enabled. This property enforces synchronization between the lifecycle states of CIs and their associated Assets, which primarily affects CIs that are linked to assets, thus excluding non-asset CIs from updates.
Resolution
To resolve this issue, disable the "Product Instance Sync (csdm.lifecycle.sync.between.ci.and.asset.activated)" system property. Disabling this property allows the lifecycle migration process to include logical CIs that do not have asset associations, effectively aligning the behavior with pre-Xanadu CSDM implementations.
Technical Notes:
- The bulk update job does not check this property, meaning bulk migration will still utilize all mappings to populate the CMDB with lifecycle data.
- After bulk migration, the system will not attempt to sync non-asset CIs if the "csdm.lifecycle.sync.between.ci.and.asset.activated" property is set to "true."
- Setting this property to "true" is not mandatory. However, disabling it can reintroduce drawbacks from the pre-Xanadu sync model, such as value flipping due to certain update actions.
- Unless you are leveraging product instance-related activities that benefit from syncing the three class types based on lifecycle values, it is generally recommended to set the property to "false."
You may find this doc helpful as well: https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle...
If this response resolved your issue, please consider marking it as Helpful and accepting it as the Solution. Your feedback helps other ServiceNow Community members find reliable answers.
Kind Regards,
Ehab Pilloor