Environment:
- Forward Networks (self-hosted)
- ServiceNow CMDB integration via NQE query
- Target class:
cmdb_ci_ip_firewall
Issue:
When mapping System Criticality (a ServiceNow choice field) from an NQE query to ServiceNow via Forward's native CMDB integration, the field consistently reports "data type mismatched" regardless of the value format used.
Attempted formats — all result in data type mismatched:
"System Criticality": "2""System Criticality": 2"System Criticality": "2 - High""System Criticality": ["2"]"System Criticality": [2]"System Criticality": ["2 - High"]- Top-level named list:
systemCriticality = ["2"]referenced in select
Question:
Is ServiceNow choice field type mapping supported in Forward's NQE→CMDB integration? If so, what is the correct NQE syntax or integration configuration to map to a choice field without a type mismatch?
Current workaround being considered:
ServiceNow business rule that sets system_criticality = "2" on insert/update when discovery_source == "Forward Networks", bypassing Forward's integration layer for that field entirely.
Any guidance or confirmation that choice fields are/aren't supported would be appreciated.
