nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Connecting in Insight 2 attributes to the same Object type during import CSV

unknown

Hi there,

I have an Insight Object type "Notification" with attributes IDNot and NameNot.
Now I'm importing in an Object Type "Keymarked" with CSV. They also have the attributes IDNot and NameNot.
I want to connect both attributes to the object type "Notifications, so I marked them in my attributes as objects and reffer to Norification.

In the import I give the IQL syntax "Label = ${IDNot}" an "Label = ${NameNot}". The result is that only 1 attribute is filled in, the other stays empty.
Is there a possibility to have both attributes filled?

Accepted answers

Jeroen Poismans

Hi Peter,

Can you elaborate with some screenshots form the OT definitions?

Jeroen

All comments

Jeroen Poismans

Hi Peter,

Can you elaborate with some screenshots form the OT definitions?

Jeroen

unknown

Hi Jeroen,

First is Object Type "Notification". Second is the setup of the attributes in my Object type "Keymarked". Third is my IQL for the download of the CSV for "Keymarked".
Only "Naam" gives data, ID stays empty

Jeroen Poismans

Hi Peter,

Ok, I think I understand what you are trying to do. A little background about Insight and the imports:

In your last screenshot, the import config, you are trying to populate the attribute Product Name with the ProductNaam value and in the next line the Product ID with the ProductID value from the same object.

That is not how the IQL selection on the import works. In your OT definition (Sleutelverwerkt) you indicate you want 2 attributes linking to a Product Notificaties object. The IQL you provide in the import defines how the correct object should be linked, not how it should be displayed.

Your ProductNaam attribute will probably be filled out because you select an object based on Label = ${ProductNaam}. The other remains empty because the IQL Label = ${ProductID} does not find such object.

So in short, in the import you defined how to link the objects, based on what attributes, not how they show up on the imported object. A linked object will always be shown as its Label field.

If you want to achieve that data from one (linked) object appears on another object, some extra logic will be involved. On Server we manage this with Insight Automation and scripting, but I don't think the Cloud version is there yet, with that functionality.

Regards,

Jeroen

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

insight

iql