Problem / Gap

Cross-schema object references are supported today in the UI and through
the Assets REST API (update object), but not in the Imports API. This
means that when bulk-loading or syncing data, object references can only be
established to objects within the same schema. If a reference needs to
point to an object in another schema-even if the schema has *"Allow others
to select objects from this schema"* enabled-the import job cannot set that
relationship.

This forces teams to either:

-

Run manual updates in the UI after imports, or
-

Write follow-up scripts using the REST API to patch cross-schema
references post-import.

Both approaches add unnecessary overhead, reduce automation potential, and
create opportunities for data drift.

Proposed Behavior

The Imports API should allow mapping references to objects across schemas,
consistent with what is already possible in the UI and REST API. For
example:

-

A "Laptop" object in the Hardware schema should be able to reference
its assigned "User" in the People schema during the initial import.
-

An "Application" in the Software schema should be able to reference
"Servers" in the Infrastructure schema in one import job.

Expected Impact

-

Consistency: Aligns behavior across all Assets interfaces (UI, REST
API, Imports API).
-

Efficiency: Enables fully automated imports and syncs without manual
or scripted cleanup.
-

Accuracy: Ensures relationships across schemas are modeled correctly
from the start, preventing data drift and duplicated workarounds.
-

Scalability: Makes it practical to manage complex, cross-domain CMDBs
at enterprise scale.