2. Create object type and attribute mapping

Specifies if the attribute should be considered a part of the object identifier. If multiple attributes are used as identifiers, the combined value will be used to identify the object and duplicates. This is used to construct an internal IQL responsible for identifying objects.

For example, if two import attributes are configured for Insight attributes First Name and Last Name, and specified as identifiers, the following IQL will be used to identify objects in Insight:

"First Name" == <first name value from source> AND "Last Name" == <last name value from source>

All attributes can be identifiers. But, for best performance, try to use the default attribute types as much as you can. For example, if using "User" attribute as identifier, we will have to query the Jira API to find users from the data source for the configured data locator. This means that Jira might be a bottle neck in this case if you have a large User directory. Try in this case to add another attribute for the user key (Default / Text) and the import will be much faster.

If you are importing objects from a CSV file into Insight, you must identify the objects by the attribute that is assigned as a label, not their name or key. The object key is generated automatically when an object is created manually or via import. Even if the object key is present in the source file (say CSV or JSON), a new object and its key will be generated instead of using the one in the source file, especially if the object key is the identifier. This could result in multiple duplicates.

Every import type needs to provide data locators. It's what Insight recognizes as a category that holds your data. For example, in CSV import, all columns are data locators.

The Insight attribute to which you want to map the data locator, and import its data.

Only used for Insight attributes of type Object (references between objects).

In this case, you need to provide an IQL to fetch the objects to set, depending on the data provided by the Data Locator. In the examples that follows, Name is a reference to the value in Insight that the referenced object has, in the attribute Name.

You can use place holders in the IQL like:

• For single attributes (max cardinality equals 1) the IQL with the placeholder could look like this:

  Name = ${DATA LOCATOR}

• For multiple attributes (max cardinality larger then 1) the IQL with the placeholder could look like this:

  Name IN (${DATA LOCATOR${0}})

  The "0" (zero) stands for all values, and 1 for the first value, 2 for the second value and so on.

For more info, see Understanding import concepts.

Description for the attribute mapping, just for convenience.

You can access other configuration by selecting the cog icon next to your attribute mapping.

Concatenator

When joining multiple data locators into one Insight attribute, this works as the default concatenator.

Regular expression

You can use regular expressions to edit the value from the import source.

For the regular expression we use Java syntax https://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html. If the regular expression does not find any match the attribute is left empty. It is possible to extract from the value given by the Data Locator by making what you wish to extract the first group in the regular expression, for example using the regular expression "(\w*)\W" (quotation marks excluded) on the value "Blue Whale" yields "Blue" to the corresponding attribute. If there is no group present and the regex finds a match the whole value is given.

Some examples: