Behavior:
Using a search query in a tool (Platform .NET API or REST API) runs into the following error:
"Wrong condition. Not parsed string..."
Solution:
The query contains special characters that are not escaped correctly.
Some special characters have to be escaped when using them (as they are) in a query. These characters are ones that can be used as control characters in a query as well: (, ), *, \, "
Examples:
Value in Field: "Invoice (in)" - Query: "Invoice \(in\)"
Value in Field: "*Test" - Query: "\*Test"
Why does this only affect certain characters?
- When you use unescaped open brackets, it is searching for closing brackets in the query.
- When you use unescaped * in a query, it is used as an indicator for wildcard search.
- When you use unescaped \ in a query, it is used as an indicator that the next character should be escaped. If there is no valid character, the query fails.
KBA is applicable to both Cloud and On-premise Organizations.
