Problem:

The current Imports API restricts mapping of object reference attributes to
only one object. This prevents scenarios where multiple related objects
need to be linked (e.g., linking a server object to multiple applications
it supports).

Proposed Solution:

Enhance the Imports API to support multi-object reference mappings. The API
should allow arrays or comma-separated values to map multiple related
objects during import jobs. Validation should confirm that all referenced
objects exist.

Example:

{
"attributeExternalId": "cmdb::externalId/id",
"attributeName": "Teams",
"attributeLocators": [
"profile.teams"
],
"objectMappingIQL": "Name IN (${profile.teams})"
}

If profile.teams contains values ["Team A", "Team B", "Team C"] all objects
containing names in that array should be linked.

Expected Impact:

-

Expands the utility of automated imports by enabling richer, real-world
relationships between assets.
-

Reduces the need for manual post-import edits to link objects.
-

Makes the CMDB more accurate and comprehensive.