This documentation is for Insight for Server/Data Center only.

It is possible to import data to an inherited structure in Insight. By specifying selector IQL for each child Object Type mapping (OT mapping) you are able to import objects to different Object types within the structure.

Create inherited structure in Insight like this:
https://documentation.riada.se/insight/latest/insight-manager-s-guide/object-type-inheritance

Create new import configuration.
Create new OT mapping, choose the parent Object type from your Insight structure.
Map the attributes.

In order to create a child OT mapping go to parent OT mapping and press the button "Create Child Object type mapping".
All parent's attributes are already mapped (they are collapsed by default, you can expand them if needed).
Now you need only map this child's own attributes if exist.

The Root Parent identifier is forced to be inherited by all the children. You can add own Identifier for any child if needed.

By specifying Selector IQL for every child you decide where in the structure your objects will be imported.

Pattern to decide order of IQL preference when importing objects:
Start with children configurations from the most specific OT and climb the inheritance tree up.
If child match -> import to child, if not -> test with next Object Type.
If none of children match:
If root parent has IQL or no child with empty IQL exist -> try with root and import to root if match.
If root not match:
If child with empty IQL exist -> try this child and import to it if match.

The common meaning of this pattern is that all the objects that don't match any IQL will be imported to the child without Selector IQL specified (you can create one and only one child OT mapping without Selector IQL) or to the root OT if no children without IQL exist.

Configuration inheritance:

All the Child OT mappings inherit the following configuration from the Root Parent:
- Selector
- Match identifier
- Unknown Values
You can't change these values for Child OT mappings.

You can specify the following configuration for every child:
- Missing objects
- Empty Values
This configuration, if specified for a child that has it's own children, will apply for all these children.

It's possible to enable/disable child OT mapping from parent Configuration menu.

Import result: