CMDB Classes are not switching via ETL

[siddheshagn]

Context: I’m moving CIs between classes: cmdb_ci_hardware_mainframe ↔ cmdb_ci_mainframe using two ETLs:
It works in DEV and TEST but fails in UAT: no records move to the destination class even though the ETL definition, entity mappings, and sys_properties were migrated to UAT. I also deleted the Source native key in UAT to force updates/inserts, but behavior didn’t change.

I have attached sys_properites snaphot along with the properties which has being used robust transform maps , along with the errors in the staging table errors from import set table I have attached the snapshot of ETL mapping as well. 

Kindly let me know for more details.

Regards,

Siddhesh Agnihotri.

[Kieran Anson]

I've run into this issue previously, SN support advised that the properties on the RTE record are multi-levelled. 

In addition to what you've set, you can add the following to set the value on the individual IRE elements, changing the property name based on the documented values

ire.input.items.settings.updateWithoutSwitch

[siddheshagn]

Thanks what I go to know is the property "glide.identification_engine.update_without_switch_enable" was set to true in UAT environment that's why it was not working there.

These are the below steps which I think might work:- 

1) We will change the property glide.identification_engine.update_without_switch property" true in dev & test respectively , same as UAT.
2) As mentioned above the new CI's are getting inserted into respective classes we will check whether the same functionality works in dev & test after changing the above property value to true.
3) Additonally, for historic data fix we will update the transform map property "updateWithoutSwitch" to true for one import and set it back to false. This ensures old CIs are fixed to the new class structure , this is are steps

[siddheshagn]

Hi Kieran,

What I got to know is the property "glide.identification_engine.update_without_switch_enable" was set to true in UAT environment that's why it didn't work.

I am suspecting below steps might work :-

1) We will change the property glide.identification_engine.update_without_switch property" true in dev & test respectively , same as UAT.
2) As mentioned above the new CI's are getting inserted into respective classes we will check whether the same functionality works in dev & test after changing the above property value to true.
3) Additonally, for historic data fix we will update the transform map property "updateWithoutSwitch" to true for one import and set it back to false. This ensures old CIs are fixed to the new class structure.