Asset CI Field Mapping form does not prevent adding mappings that are already covered by the Install Status- and Hardware Status-specific Mapping tables

For example, it is possible to add a Field Mapping for CMDB Status [cmdb_ci.install_status] to Asset Status [alm_asset.install_status]. This will override the Install Status- and Hardware Status-specific Mapping tables, and cause CI field numeric values to be copied into Asset fields, which expect string values, so appearing as invalid choices like "(100)".

Steps to Reproduce

  1. Asset - Administration - Asset-CI Field Mapping, click New
  2. Asset Field = State, Configuration Item field = State, Save
  3. Update a CI to e.g. Status = Absent

The linked Asset will now have broken invalid value "100", instead of the expected equivalent asset choice value for absent as defined by the other status specific field value mapping tables.


This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available.

If you have added custom field mappings for any of these fields, please remove them to resolve issues caused by them:

Related Problem: PRB1394774

Seen In

There is no data to report.

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-04-13 08:47:08