Issue Summary

When a reference attribute is also an identifier, there can be cases when AQL will return multiple objects. For those cases, duplicate objects are being created - instead, they should be updated, or detected as identical objects depending on the import configuration

Steps to Reproduce

1. Configure the import mapping to have references, say 2 OTs OT1 and OT2
2. Add a reference attribute which is also an identifier
3. Add an AQL (say in OT1) which will be used to search for the objects of other OT (say OT2)
4. Add existing objects to the schema such that AQL will return multiple objects
5. Run the import

Example:

EXAMPLE MAPPING:

OT: Store
    Attrs: 
      Name (identifier)
OT: Box
    Attrs: 
      Name, (identifier)
      Store (identifier) (ref to OT Store Name=${box_store_name})
OT: Lane
    Attrs: 
      Name, (identifier)
      Store (identifier) (ref to OT Store Name=${lane_store_name})
      Box (identifier) (ref to OT Box Name=${lane_box_name}) 

EXISTING OBJECTS:

Store: 
[Name=s,...] [Name=s1,....] 
Box: [Name=b,store=s...] [Name=b,store=s1....] 
(is possible as name,store are id) 

Lane: [Name=l1,store=s,box=b] [Name=l2,store=s,box=b] [Name=l3,store=s1,box=b] (is possible as name,box,store are id)
 

Now when we run the import again for Lane OT, duplicate objects are created for lane

When AQL “box=b” is run, it finds 2 box objects, both are returned

Expected Results

Duplicate objects should not be created.

Actual Results

Duplicate objects are being created, and updated/identical objects are 0 

Workaround

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