Posted Wed, 19 Sep 2018 07:43:55 GMT by Gilles Sauvagnat Président


Since V7 update using wild card characters such as * or ? returns a "Wrong condition. Not parsed string 'blabla*' for field 'DocuWareFulltext'

Is it a feature, a bug, a user error ?



Posted Wed, 19 Sep 2018 11:10:11 GMT by Joe Kaufman Manager


That is weird if they changed that -- but might I ask why you would need a wildcard like "*" in full-text search? Isn't full-text searching inherently a "contains" situation (i.e. a term with wildcards on both sides, *<term>*)? To put it another way, I cannot imagine a search term with an asterisk returning anything other than what is found for the base search term?

Not sure about "?" -- does something like a Google search generate different results based on positional wildcards? I'm off to test!



Joe Kaufman

Posted Wed, 19 Sep 2018 11:30:59 GMT by Ingo Bechtle Manager Support Team BLUE EMEA

Hey everyone,

just wanted to tell you that indeed this change was not intended and is classified as a bug.
The behaviour is already fixed in the next update.


With best regards

Ingo Bechtle
Software Support Specialist Team BLUE EMEA

Posted Wed, 19 Sep 2018 12:55:04 GMT by Gilles Sauvagnat Président


Thanks for the speedy answer. Fix will be installed asap


Imagine you want to search for a three digits numbers but you are not sure of the second digit 3?0.00 will solve the issue.

For *, I found that in severeal occasion it returns a different result with and without a wild card. For instance ge will return storage and ge* will return the previous result, plus germany gestion genco and so on (unless you set up the wild card as a default in the field search dialog

At least that was the way it worked in 6.12



Posted Wed, 19 Sep 2018 13:14:57 GMT by Joe Kaufman Manager


That makes complete sense -- a "whole word" sort of motifier. Though, in 6.11 if I search for "ant" I got 22 documents highlighting the word "QUANTITY". If I threw asterisks on either side of "ant" I got over 200 hits, also finding the word "ATTRACTANT". I am not sure I understand why a straight "ant" found inside QUANTITY would not also be found in ATTRACTANT. A "contains" should be a contains whether a search term is found at the start, middle, or end of a word.

Definitely differing results, though!

The "?" makes complete sense, though -- that is a good example you offer.



Joe Kaufman

Posted Fri, 21 Sep 2018 03:32:30 GMT by Gilles Sauvagnat Président


More info here




You must be signed in to post in this forum.