Potential issue with Unique IDs for single-property classes

[DnOberon]

Bug Description

Adam Fagan from APL told me about a bug where if nodes were coming in with a single property, and that property was assigned as unique ID, the node was being recreated upon update instead of updating with new versioned information. The bug disappeared with a two-propertied class.

Steps to Reproduce

Create the following:

• a single property class
• a multi-property class

Import the following data:

• a set of single-property objects (mapped to the single class), slightly alter, and re-upload
• a set of single-property objects (mapped to the multi-class), slightly alter, and re-upload
• a set of multi-property objects (mapped to the single class), slightly alter, and re-upload
• a set of single-property objects (mapped to the multi-class), slightly alter, and re-upload

Impact

Could be frontend or backend. Most likely something to do with original_data_id not being properly assigned to the created nodes. Perhaps contact [email protected] for more information on what his test case was.