-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Low
-
Component/s: Assets - Import
-
None
-
1
-
Severity 3 - Minor
Issue Summary
Asset import referencing object type attribute that includes child objects is not working as expected.
Steps to Reproduce
1. Create the following object types:
1.1. Users:
- Attributes: Name and Devices.
1.2. Devices:
- Attributes: Name
1.3. Create Phones as a child object type of Devices:
- Attributes: Name
1.3.1. In the Device attribute in the Users object type, check the option Include Children
3. Manually create an object in the Phones (e.g, iPhone) and another in Users (e.g, John). With the User object referencing a Phone object.
4. Create an import mapping using the following CSV file:
Name,Hardware Peter,iPhone
5. In the Devices attribute mapping, use the following AQL:
label = ${Hardware}
6. Run the import
Expected Results
The object Peter is created with the iPhone object in the Device attribute
Actual Results
The object Peter is created with an empty Device attribute.
Workaround
In the attribute mapping, use the following AQL:
objectType in objectTypeAndChildren("Devices") and label = ${Hardware}
- duplicates
-
JSDCLOUD-16662 Assets import for reference object attribute not working when using AQL referring to another attribute in the reference object
-
- Closed
-
- is caused by
-
JSDCLOUD-16656 Assets inbound references don't show in linked objects and aren't retrieved in AQL queries
-
- Closed
-