importing assets

[Samuel Boerhoop]

I am using the import function with csv with a mapping table:

Mapping table 

identifier: CI Name

Data source field needs updating: Cleaning Date

2 item in the mapping table

Say in the database I have :

CI Name, IP, Cleaning date, etc... more attributes

ICOMx1, 192.168.2.25, 10 march 2026

ICOMx2, 192.168.2.24, 11 march 2026

Importing from csv

CI Name, Cleaning Date

ICOMx1, 14 march 2026

ICOMx2, 15 march 2026

ICOMx3, 16 march 2026  < should be skipped, instead it adds it in the datebase with only > CI Name and Cleaning Date

Then the import function add also the ICOMx3 in the database, while my identifier is fixed on CI Name and should not add this one to the database?

What I am doing wrong?

[Samuel Boerhoop]

@Arkadiusz Wroblewski : That is exactly in how you describe it. I don't want to import missing objects, only object what are currently in the database. 

From other import function wont work either?

This is a database of 1000 assests. We are importing data from Genetec export also via the import function, of 4000 assets. Also making export out IBM (maximo) and importing in Jira assets... 

[Arkadiusz Wroblewski]

@Samuel Boerhoop 

Please Provide Screenshot from Audit of Last Import.

[Arkadiusz Wroblewski]

Thanks for the screenshots. Your mapping looks correct to me: CI Name is marked as the identifier, and that identifier is used to decide whether Assets should update an existing object or create a new one. If the identifier matches an existing object, it is updated. If it does not match, Assets creates a new object. So based on Atlassian’s current docs, I would still expect ICOMx3 to be created, not skipped. Now i explain why.

The Missing objects = Ignore setting does not change that behavior. Atlassian documents that this setting only affects objects that were previously imported by the same import structure and are now missing from the current source. It is not an update existing only switch.

So from what you showed, your Mapping is Ok. But you mixing Use Case. If your goal is strictly update existing assets only, I do not see a native option here that says skip rows that do not already exist in Assets. The practical way is to filter those rows out before the CSV import runs.

[Arkadiusz Wroblewski]

Hello @Samuel Boerhoop 

Please share Screenshot from Mapping.

In Assets Cloud, the identifier (ID) is used to match an incoming row to an existing object. If a match is found, the object is updated. If no match is found, Assets creates a new object instead. So I would not expect ICOMx3 to be skipped just because CI Name is set as the identifier.

The Missing objects setting is a different thing. That only applies to objects that were previously imported by the same import structure but are not present anymore in the current source. It does not stop new rows in the CSV from being created.

So from what you showed, I do not think you are doing anything wrong. If your goal is really update existing objects only, then the safer approach is to filter the CSV before the import so rows like ICOMx3 are not included.

Key Fact are Right Mapping and Unique ID Attribute:

Take a look on following KB as it should help you: Create Assets objects from data using object type mapping | Assets | Atlassian Support