ServiceNow CMDB Integration — Choice Field Type Mismatch for System Criticality

Choice fields aren't supported by the native CMDB integration today. That's the reason every format you tried returned the same "data type mismatched" error.

Today, the integration types each value based on its NQE column type and sends it to ServiceNow's IRE. It handles string, integer, float, boolean, and IP address fields. Choice fields aren't in that set, so IRE rejects the payload regardless of the value you send.

That's also why changing the value didn't help. "2" and "2 - High" are both strings, so they go over the wire as the same type. 2 as an integer changes the type but still isn't what the choice element expects. And the array formats aren't valid input for a single-value field. None of them match what IRE wants for a choice field, so you get the same rejection each time.

The error message should have told you the field type was the problem instead of a generic mismatch. That's on us, and it's something we're improving.

Your workaround is the right approach. A business rule that sets system_criticality on insert/update when discovery_source == "Forward Networks" keeps the criticality value in ServiceNow where the choice list lives, and it avoids the integration for that field entirely. This is a sound pattern and how I’d handle this.