Issue Summary

When a duplicated Data locator exists in the source, Assets import detects the duplicated entry based on the identifier and does not create duplicated objects ( expected). However, for some attributes and if the cardinality is configured accordingly, attribute values from both the duplicated entries are added ( unsure if it's expected). Following the same logic, the attributes should be removed by the import if both the duplicated entries have empty values. However, Assets import does not remove the attribute values for this specific scenario( not expected).

Steps to Reproduce

This bug has been tested on object schema import, database import and CSV import.

1. Set up an Assets import. For this example, we use CSV import.
2. Ensure that when a Data locator is empty, the import removes the attribute value.
3. Create a CSV file for import and include an example where there are multiple sources for one of the objects. For example, "Asset Name" will be the identifier and there are two entries of "Laptop 01".

   Asset Name,Asset Type,Serial Number,Location,Purchase Date,Owner
   Laptop 01,Laptop,SN123456,Sydney,2023-01-15,JIRAUSER10000
   Laptop 01,Laptop,SN123457,Melbourne,2023-02-10,JIRAUSER10103
   Monitor 01,Monitor,MN654321,Sydney,2022-12-05,JIRAUSER10101
   Phone 01,Phone,PH111222,Brisbane,2023-03-20,JIRAUSER10102
   

4. Import and verify the objects created and the attribute values.
5. Edit the CSV file and clear the values of all columns except for the "Asset Name". The CSV file content should look like this now.

   Asset Name,Asset Type,Serial Number,Location,Purchase Date,Owner
   Laptop 01,,,,,
   Laptop 01,,,,,
   Monitor 01,,,,,
   Phone 01,,,,,
   

6. Run another import and verify if all objects have the attribute values removed accordingly.

• With the first import, only 3 objects are created. One of the "Laptop 01" is considered as duplicated and only the values of another "Laptop 01" are imported. For example, for "Laptop 01", only the values of the second row should be created along with other objects.

  Laptop 01,Laptop,SN123457,Melbourne,2023-02-10,JIRAUSER10103
  

• With the second import, all 3 objects have all values except "Asset Name" removed.

Actual Results

• With the first import, only 3 objects are created. One of the "Laptop 01" is considered as duplicated and only the values of another "Laptop 01" are imported, but the values for "Owner" are added from both rows.

  Laptop 01,Laptop,SN123457,Melbourne,2023-02-10,JIRAUSER10000||JIRAUSER10103
  

• With the second import, "Laptop 01" doesn't have any values removed but other objects are updated accordingly.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.

Versions Tested

Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: