CSDM life cycle mapping

[priyasunku]

I am trying to setup life cycle mapping . we have custom status choices on CI table which are not used for Asset.

When i try to setup the life cycle mapping it gives me a discrepency report saying there is no valid asset-ci mapping found.

my question is why do we need to create a asset- ci mapping even when i am not using those status chocies for Asset.

Could someone help here

[ayushraj7012933]

This is expected behavior. The Lifecycle Mapping validator checks for a valid Asset-CI mapping even if your custom status is only used on the CI. The lifecycle framework is designed to maintain consistency between Assets and CIs whenever they are associated, so it validates the complete mapping configuration.

If a corresponding Asset-CI mapping is not available, the validator reports it as a discrepancy because it cannot determine how the linked Asset lifecycle should be handled.

To resolve the issue, create a valid Asset-CI lifecycle mapping for the custom CI status, even if the Asset does not actively use that status. This satisfies the lifecycle validation and ensures the configuration remains consistent. If the CI is never associated with an Asset, the discrepancy can generally be treated as a validation warning rather than a functional issue.

[priyasunku]

Hi @ayushraj7012933 

Thank you so much for the reply.

to your last statement 'If the CI is never associated with an Asset, the discrepancy can generally be treated as a validation warning rather than a functional issue.'  there is no other way than fixing the discrepency report when i click on ' enable life sync'. is there any way to ignore it and continue the sync.

[ayushraj7012933]

hi @priyasunku 

There isn't an out-of-the-box option to ignore the discrepancy report or bypass the validation when enabling Life Sync. The validation is built into the lifecycle synchronization process and must pass before Life Sync can be enabled.

The OOB approach is to complete the required Asset-CI lifecycle mappings, even if some of the custom CI statuses are not actively used by Assets. This ensures the lifecycle configuration is considered valid by the framework.

If those custom CI statuses are not intended to participate in lifecycle synchronization, another OOB option is to review your lifecycle mapping configuration and include only the lifecycle states that need to be synchronized. However, there isn't a supported way to skip or disable the validation itself.