-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Component/s: Assets - AQL
-
1
-
Minor
Issue Summary
Using the keyword EMPTY within a like or the equals = operator in an AQL removes the quotes characters when being used in the Advanced AQL section to Filter objects within your schema.
Steps to Reproduce
1) Make sure that under your Schema Tree you have an abject with at least one attribute with Type Default and Type value Text defined. For further reference lets call our Text attribute: "Example Text 1"
2) Make sure to fill out the text attribute of a couple of objects with the following string: "EMPTY" (write it without the quotes)
3) Go to the Objects view in the UI and filter using the following Advanced AQL:
"Example Text 1" LIKE "EMPTY"
4) Notice that if you try to edit the Advanced AQL filter you'll notice that the quotes characters are removed from the like "EMPTY" part of the AQL:
"Example Text 1" LIKE EMPTY
leading for the green checkmark to change for a red cross and the AQL no longer being valid.
Expected Results
The quotes are not removed from the EMPTY keyword and the AQL stays the same
"Example Text 1" LIKE "EMPTY"
Actual Results
The quotes are removed from the EMPTY keyword behind the like operator and the AQL is changed to something like:
"Example Text 1" LIKE EMPTY
Workaround
Avoid using variations of the word empty (EMPTY, Empty) when filling out attributes of type text to avoid issues with the like operator and the EMPTY keyword.
- blocks
-
JSDCLOUD-16344 Trying to Bulk Edit objects from the UI when Advanced AQL filter contains like EMPTY results in "An unknown error occurred"
-
- Closed
-