Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Insight: import problem with childobjects

Sven Rühlemann
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 16, 2018

I have a problem with my import of clients from my software deployment database. I get duplicate objects after i moved them to an objectchild.

My object structure in insight:

Object type Clients (attributes are set and inheritance is active)
> Notebooks (childobject of Clients)
> PC's (childobject of Clients)

The import creates new objects (client1, 2, ...) below clients. After import i move client1 to notebooks. Next time the import runs, it creates a new object client1 below Clients instead of updating the existing object.

After set the attribute name to unique I've got an import error. The attribute name must be unique.

Can someone please explain to me how I must set the iql-filter of the import, so that the childobjects below Notebooks and Clients are included?

Regards

1 answer

0 votes
Yinon Negev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 25, 2018

Hi Frank,

The Reason you get this behavior is because you move the Imported Client Objects into the Child Object Type, then import again to the Parent Object Type.

The way this should be handled is by defining two Object Type Mappings in your Import: one for the Object Type "Notebooks", and one for the Object Type "PC's". For each Object Type Mapping, you should first configure an IQL filter, in order to allow only the relevant Objects to be mapped to this Object Type.

The IQL can be something like "Client Type" = "Notebooks" for the Notebook Object Type, where I used an attribute called "Client Type" but you may have a different name - this Attribute will store the value differentiating between Notebook and PC's, so your data source should have this information in order for the filtering to work.

The IQL for the "PC's" Object Type Mapping, should then be something like: "Client Type" = "PC's".

This will Import the Objects directly into "Notebooks" and "PC's" and based on the Identifier selected in each Object Type Mapping - no duplicates should be created, and existing Clients will be only updated.

In our documentation: General Import Concepts there is a short 
Video specifically explaining how to achieve your requirement.

cheers,

Yinon

Team Riada

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events