How to automatically link multiple asset objects to an employee attribute during Assets import?

[田中優貴]

Title
How to automatically link multiple asset objects to an employee attribute during Assets import?

Body
I am working with two schemas in Jira Service Management Assets:

• Employee List schema
• Asset List schema

In the Employee schema, there is an attribute called “Owned Assets (Object)” that is configured as an Object type attribute and allows multiple values. This means it can store multiple asset objects from the Asset schema for a single employee.

---

What I have done so far:

• Configured the “Owned Assets (Object)” attribute to allow multiple values.
• Set up the import configuration so that the Employee CSV column “Owned Assets” references objects in the Asset schema.
• The reference key is the Display Name in the Asset schema, which is unique (no duplicates, acts like an ID).

---

Current issue:
When I run the import, no asset objects are linked at all, even though the Display Name matches and the attribute supports multiple values.

---

Additional details:

• Jira Service Management Cloud (latest version)
• CSV uses “||” as the delimiter for multiple values
• Reference key: Display Name in Asset schema (unique)
• Expected result: Each employee should have multiple asset objects linked automatically
• Screenshots of the attribute settings and import structure will be attached (UI is in Japanese, but I will add English captions)

---

Example CSV:

"Employee ID","Name","Assets"
"EMP002","Kato Yui","iPhone 13-AS54142315||iPhone 14-AS16914203"

---

Questions:

• Is there a specific setting in the import structure to handle multiple object references?
• Are there any limitations or best practices for using “||” as a delimiter?
• Why might the import result in no linked objects even though the Display Name is unique and the attribute supports multiple values?

[田中優貴]

Thank you for your response to my previous message. I also apologize that the attached file ended up being in Japanese.

I tried what you suggested, but I couldn’t make it work. What I’m attaching now is the content of the CSV file and how it appears in the display. It’s related to the object. Could this have caused any issues?

[Marc -Devoteam-]

Hi @田中優貴 

I assume your import structure is correct, but you need to set the values as follows:

"iPhone 13-AS54142315"||"iPhone 14-AS16914203"

You where missing the quotes for closing the 1st option and opening the 2nd option.

Also see, https://support.atlassian.com/assets/docs/prepare-your-data-for-importing-into-assets/ 

[Marc -Devoteam-]

Hi @田中優貴 

How is you import mapped in assets, seem like the field is set as a normal field and not as a reference

[田中優貴]

I'm sorry for using an image that might be hard to understand.
I'm currently using an Object Type field in the configuration.

[Marc -Devoteam-]

Hi @田中優貴 

So you the attribute Owned Asset is a referenced object to another object type in the same schema or other schema.

On the import, how did you configure this, what are the settings on the import you made?

[田中優貴]

Thank you for your support

• The data source field Owned Assets is mapped to the destination attribute Owned Asset (Object type).
• Reference mapping is configured to use the Display Name from the asset list (Simple).
• Object reference is managed in another schema, enabling cross-schema linking for assets.
• The data source field, the destination attribute, and the referenced Display Name all contain the same value: the asset name.

[Marc -Devoteam-]

The attribute owned assets, what is the cardinality set to?

Can it contain more than "1" referenced object?

[田中優貴]

I’ve set the cardinality to the maximum value.

[Marc -Devoteam-]

Hi @田中優貴 

Could it be language related, as it looks like the pipe sign is converted to - in your example.

is the CVS in UTF-8 (default), UTF-16, ISO-8859-1, ISO-8859-15, Windows-1250, Windows 1252?

Can you execute the same on sandbox, with language set to English?

Otherwise, reach out to Atlassian Support.

I provided you the information based on the documentation and this should work.

[田中優貴]

Thank you so much for your detailed support — I really appreciate it.
Apologies for the delay in getting back to you. Due to time constraints, switching the sandbox environment to English will need to be done at a later date. I’ll follow up once that’s ready.
As for the CSV file, it is encoded in UTF-8 and uses comma delimiters.