Why are life cycle mapping legacy field updates not accepted?

[Rebecca L]

I am working on completing an incomplete setup of CMDB, currently at the point of 'Migrate to CSDM life cycle standards' and am seeing oddities in my company's instance.  I compared my finding to a PDI and found something similar.  

When the two records below are opened, the Legacy field value does not match any selectable options. 

In my company instance, updates to the legacy field value are not accepted.   

What is the reason for this?

[SebastianKunzke]

Could you please provide use more details, why an update is not accepted? What kind of error message does appear or is the field just read-only?

In addition could you please verify the field choices for the field "status". Maybe your company did customized them and because of that the current mapping to the OOTB values is not valid.

Thank you.

[Rebecca L]

When updated, no system message appears on-screen.  The update appears to function as normal but when I return to the record nothing has changed.  So, that is what I mean by "not accepted".  I have not yet looked in the log.  

The possibility that my company did customize them was my reason for comparing to an OOB instance, my personal developer instance (PDI).  The screen shots provided are of the PDI.  I am trying to get a better understanding by learning why the behavior occurs in the OOB instance so I can use this for comparison to my company's possibly customized choices.  

I appreciate your response, and any advice to help me move forward with a better understanding would be greatly appreciated.  

[SebastianKunzke]

Okay, now I understood it. In my instance I also face the same issue on the field "install_status". It seems, that the form is not loading the saved choices correctly. The value of the status was saved, but it is not displayed correctly. You can see that the value is stored, because you can see in the column the field value "7", which is the value of the status "retired".

I would suggest to open a support ticket at the ServiceNow support. Please feel free to give me a short response, when you received an answer.

Thank you.

[Steve MacDonald]

@Rebecca L  - Is the mapping working correctly, even though the display in the form is incorrect? 

On my PDI loading the Life cycle mapping form is slow, so I can initially see the appropriate value (2, for Non-Operational) before it changes to the incorrect value of 'Operational', and the XML seems to be correct, but am just wondering if it is working correctly in usage of the mapping. 

Thanks, Steve