-
Bug
-
Resolution: Fixed
-
Low
-
5.4.6
-
5
-
Severity 3 - Minor
-
Issue Summary
Object Mapping in CSV Import using LIKE and IN is Case Sensitive - should be case insensitive as per AQL Documentation
This is reproducible on Data Center: (yes) / (no)
Steps to Reproduce
- Create an Object Type: Superheroes with following Attributes
- Create an Object Type: AvengerGroup with following Attributes. Set the cardinality of 'Email-ID' and 'Contact-ID' to unlimited
- Create a CSV Import to import Object to Object Type: Superheroes. File: Superheroes.csv
- Create a CSV Import to import Object to Object Type: AvengerGroup. File: AvengerGroup.csv
- Set the Object Mapping as shown in the screenshot
- Import the Objects
Expected Results
Objects are imported with all Attributes updates irrecpective of Case Senstive
Actual Results
Object are imported but only those attributes are updated which has same Case Sensitive
Workaround
Make sure the Case Sensitivity is followed with the content in CSV
- is related to
-
JSDCLOUD-14801 When multiple values exist in the import source, the object type attribute reference AQL becomes case sensitive in Assets imports
-
- Gathering Impact
-
- links to
- mentioned in
-
Page Loading...