Search Widget 4.25 - 'Deep' searching feature layer attributes?

Question

Hello Javascripters,

I'm having a slight issue with the newest JSAPI (4.25) search widget and wondering if I'm missing something.  The 'what's new' documentation says that:

In order to make the Search widget faster and more efficient with a layer-based source, we removed the leading wildcard in layer-based source searches...

This is causing issues with searching beyond the first word in an attribute column.  For example, I have a sentence stored in a column that I'm searching on...'The Elk Horn Lodge...' is how it begins.  Can cannot get results for anything but 'The' in the search box.  There doesn't seem to be anything obvious to undo this new 'enhancement'.

In 4.24, searches for 'Elk', 'Lodge' or anything else that was in the attributes worked fine.

Any help would be great.

Thanks!

SebastianKrings · Answer

Another possible way may be using full-text-index in combination with searchWidgets exactMatch = false property.
Unfortunately it only seems to change from a "field-start-with"-condition to "any-word-in-field-starts-with".

Lets say a features name is  "My SearchField" then searching by "Search" would work since "SearchField" is a word inside the field and starts with the searchterm "Search".
While searching by "Field" would not work since "SearchField" is still a work in the field but does not start with the search termn "Field"

I tried to use the interceptor and set a breakpoint.
The interceptor is simply placing a '%' infront of the search term.

Suprisingly, right before doing the interceptors magic the request options already do contain a like with % before and after the search term. Unfortunately is still does not

Any ideas on what is still going wrong?

We are using 4.34

MRietveld · Answer

This should also be sufficient

layerSearchSource.prefix = "%";

GreggRoemhildt2 · Answer

@MichaelSnook  here's another alternative approach I found with the 4.x api - it basically uses the esri request interceptors to intercept matching /query:

const log = debug('interceptors');

// fix the search query issue
esriConfig.request.interceptors.push({
    urls: /\/query/,
    before({ requestOptions }) {
        if (/LIKE '[^%]/g.test(requestOptions.query?.where)) {
            log('like request intercepted', requestOptions);
            requestOptions.query.where = requestOptions.query.where.replace(/ LIKE \'/g, ' LIKE \'%');
        }
    }
})