CSDM lifecycle mapping table and class inheritance doesn't work

[Amar_Be]

Hi,

The Life cycle mappings table provide a mapping for the legacy status fields of the CMDB classes.
In case a class do not have a specific mapping defined for it, the system should go trough the class's parents list until it find a mapping.

So having the mapping on class cmdb_ci should be enough to handle all the CIs.

But when I disabled all the mapping but the ones for cmdb_ci, I get the value "To Be Determined" into the CSDM status fields.

Is there is something to add, configure or correct to make use of the inheritance of the classes?

Thanks

[emir]

//no mappings match on legacy fields, set to "To Be Determined"

check your existing values and the map, while they may appear the same check actual values on the CI you are expecting to change and that they are the same on the root table

[Amar_Be]

Thanks for your answer.
I've disabled all the mappings except the ones for cmdb_ci. With only the cmdb-ci mappings active, I get the error when I change the operational status on a cmdb_ci_computer item..

If I create a mapping for the cmdb_ci_computer class then it works as expected.

I create the mapping for cmdb_ci_computer by using "insert" so I'm sure I'm using the same values.

It's on a PDI where I've changed nothing else so it is an OOTB configuration.

Is there a way to trace and debug the script used to set the CSDM values without modifying it?

[Amar_Be · Accepted solution]

I've found the reason why it is not working;

If a mapping is marked as inactive, it is still taken into account by the update script but its value is not used.

To ignore a mapping, it must be deleted.

So what is the utility of having the "Active" attribute? 🙄  It would be very simple to only retrieve active mappings in the update script.

[emir]

thats sounds like a defect for sure