-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Highest
-
Component/s: Assets - Import - Rearchitecture
-
3
-
Severity 2 - Major
-
28
Issue Summary
Assets import for reference object attribute not working when using AQL referring to another attribute in the reference object
Steps to Reproduce
- Create 3 different object type , 1 as parent object type (Corporate Assets) with 1 child object type ( Hardware ). Then , create another object type called (People)
- Make sure the parent attribute shared with the child object type.
- Create reference object type attribute in Corporate Assets , called "Device Primary User" and refer to People object type.
- In People , create a new reference object type refer to "Corporate Assets" and ensure to tick the "Include child object" , name it "User Assets"
- Then , create a People object without updating the "User Assets"
- Create new object in Hardware and update the "Device Primary User" value with People object
- Now , create a CSV file to import to People object type , with "Name" and "User Assets" . Update the Name with the People object and leave other empty.
- Create import configuration and map for People object type :-
| Data source field | Destination attribute | Advance AQL |
|---|---|---|
| Name | Name | |
| Name | User Assets | "Device primary user" = ${Name} |
Expected Results
People object udpated with the "User Assets"
Actual Results
Object not updated
Workaround
No workaround
- is duplicated by
-
JSDCLOUD-16718 Asset import referencing object type attribute that includes child objects is not working as expected
-
- Closed
-
- mentioned in
-
Page Loading...