V7 Full Text Search with wild card-1537350235

Hi,

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 ?

Regards

Gilles

Giles,

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!

Thanks,

Joe Kaufman

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
DocuWare

@Ingo 

Thanks for the speedy answer. Fix will be installed asap

@Joe

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

Regards

Gilles

Gilles,

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.

Thanks,

Joe Kaufman

Joe

More info here

https://docuwarekb.microsoftcrmportals.com/knowledgebase/article/KBA-35961/en-us

Regards

Gilles