CSDM Life Cycle Mapping enable life sync => which fields get evaluated

[thomasbueck]

Hi,

we want to enable CSDM Life Cycle Mapping and when I press "Enable Life Cycle Mapping" I get a list of issues I need to solve.
There are some legacy status values found which are not used anymore and I don't want to create additional mappings for these.
I changed the values for those CIs and have also deactivated the sys_choice records, never the less I still get these values listed as a conflict I need to solve.

My question here is what records takes SN into account to generating the first part of the "Discrepancy Report"?

Thanks for your support
Thomas

[CasperJT]

Hi Thomas,

Even if the values are not in use they are still there. The system likely checks the dicitonary entry and its choices. Then it evaluates based on all active choices. If a choice is active it could theoretically be selected even if you do not want it to.

Depending on your situation you could deactivate the legacy states you have no use for or you will need to map them.

Hope this helps.

//CasperJT

[thomasbueck]

Thanks Casper, but the the choices in the dictionary are from sys_choice and they are deactivated for cmdb_ci and all extended tables

[CasperJT · Accepted solution]

Quite interesting. Perhaps it doesn't even consider active true/false, but simply whether the choice exists.

[thomasbueck]

Yes - that's it.
Deleting the choices solves the issue
Thanks - always good to get a different perspective.