Default *Contains* Search (glide.ui.goto_use_contains) not working with Madrid

[Tschewski]

Hi guys,

we have a issue with the default search behaviour in the backend. We want the user to search with *contains* by default and created the following Property as described:

Name: glide.ui.goto_use_contains

Type: true/false

Value: true

But in the end the property is not working. The search in lists is still using *starts with*.
Our instance is new and created for us on madrid. So there is no plugin like list V3 activated.

Any help would be appreciated! 🙂

Thanks a lot!

[Michael Fry1 · Accepted solution]

When you use the Search next to the New button, does it use 'contains'? I don't think it works when using columns search.

[Tschewski]

Hi Michael,

the search next to the NEW Button works with contains. It copies the search to the columns search.

BUT: In a prior release (Jakarta) I created the same property and it still works (Madrid) in column search, tool. In that implementation we activated the Listv3 Plugin, which isn't available in the current project with madrid.

See this screen for it:

Thanks,

Dominique

[Tschewski]

An official question to servicenow gave us the answer that is it officially not supported, as you said...

Interessting that it working in previous release ith listv3 🙂