List collector Search Behavoiur?

[mahi4889Snow]

Is there a way to change the default search behavior of the List Collector catalog variable to be "contains" instead of "starts with"? I know that I can use a wildcard in the search field, but I'm trying to make it a bit easier for the end user.

Thanks in Advance.

[Jim Coyne]

It all depends on the instance's configuration. You can set a table's default autocomplete search to be "contains" and the List Collector search will use that setting:
http://wiki.servicenow.com/index.php?title=Auto-Complete_for_Reference_Fields#Contains_Auto-Complete_Search

But, there is a new setting that disables contains searches:
http://wiki.servicenow.com/index.php?title=Auto-Complete_for_Reference_Fields#Improving_Auto-Complete_Queries

You can see that I have it setup in demo11. I've added a "sys_user.autocomplete.contains" preference and disabled the "glide.ui.ref_ac.startswith" property. Check out the "Reference Test" catalog item. Type in "red" in the List Collector search box and users with the string "red" in their name will appear.

I'm assuming that SN has found that a lot of clients were using the contains searches and it is causing some efficiency problems at the database level so they added that new property to override the contains searches.

[Pastupe]

Thank you, this helped me to solve my requirement.

I created user preference for autocomplete for particular table and it works

/Petr

[Johannes Mweli]

Hi Pastupe,

Would you please share how you were able to get this to work. I have the same requirement I need the list collector variable to search using the "contains" instead of the "startsWith". 

Thanks,

Johannes

[mahi4889Snow]

Hi ,
Thanks for your information.

We are running Berlin release instance only even though we couldn't find "glide.ui.ref_ac.startswith" property. But i just created the new User preference to custom table and assign the "contains". Its works fine as we expected in List collector search without having "glide.ui.ref_ac.startswith" property. Is there any impact?

Note:
We already have "glide.ui.goto_use_contains " property in our instance.