Issue Summary

When performing an assets data import, the import process incorrectly updates the object's timestamp to reflect a recent modification, even though no actual changes have been made to the object. Additionally, the activity history for the object does not log any new changes, further confirming that the object itself remains unchanged.

The behavior was first noticed following the migration to the new assets architecture.

Steps to Reproduce

The following is a test/setup to demonstrate what was found in the customer environment which demonstrates this behavior. 

NOTE: It may be enough to simply note that when performing an import, the updated value for objects that have not been modified is updating.

Full setup / steps to demonstrate the behavior 

• Create a CSV that contains the following.
  Name,State
• TEST1,Active
• TEST2,Active

Create or use an existing object in one of your schemas that has these attributes (Name, State)

Create an automation rule that...

• Triggers on Object Updated
• Sends an email to yourself that indicates object.key was updated
• Set the threshold to 0

Create a CSV import and mapping to import the data.

In the Edit object type mapping, set Missing objects to Update, Attribute to edit will be State, and the value will be NULL

Complete the source/destination attribute mapping for the object

Test

1. Import the data and confirm it shows up in the schema
2. Confirm no email was received from the automation rule
3. Update the CSV by removing the record for TEST2 and save the file
4. Edit the import structure and remove / re-add the CSV file and save
5. Import the data and confirm the value for TEST2 now displays NULL in the schema
6. Confirm that an email was received, indicating the object was updated
7. Confirm that the object activity reflects the object update i.e. "Active -> NULL"
8. Making no additional changes, perform additional import actions

Expected Results

• Object history will not show any additional updates for TEST2 in the Activity history
• No additional emails will be sent indicating that the TEST2 object was updated via the Automation
• The "Modified" date will remain unchanged for the object as shown in the lower right of the object properties screen

Actual Results

• Every import action results in the Modified date for the object being updated
• Every import action following the initial import results in an email sent via the automation
• No matter how many import actions are performed, no additional update actions are added to the Activity history (which is correct, because the object is not being updated)

Workaround

None known at this time.