nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Tokenized false makes property case-sensitive

yogeshpj

Hi All,

When i make property tokenized true then it is lucene search results me in case-insensitive manner.But when i make property tokenized false then it gives me in case-sensitive results. But i want case -insensitive result in this case also ? How can i achieve this ?

Any help will be appreciated !!!

Thanks
Yogesh Prajapati

Find more posts tagged with

Comments

mitpatoliya

I do not understand your requirement why cant you just keep the value as true and keep it case-insensative.
Also there is one more option as where you can specify value as <tokenised>both</tokenised> try that as well.

martijn

Hi,

I had the same problem, and wanted tokenised=false, otherwise my search facets/filters would split my fields into keywords. For example, a name field: 'Burg, M.D.' would display the facets 'Burg', 'M.', 'D.' 'Burg M.' for the custom name field.

Using tokenised=both resulted in facets having the whole value, but searching is still case insensitive.