• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 95 subscribers
  • Views 4230 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Default Search criteria for Product Searches

Craig Bolte
over 7 years ago

 1IM 7.1.2.  When you go to the request page in ITShop, the search field (highlighted below) defaults to using a "Starts with" search.  How do you change that to use a "Contains" search?  This would allow the user to type "test" in that box and it would find products that had that anywhere in the name.

Thank you,

Craig

 

  • 0 over 7 years ago
    User can always type *searchterm or *searchterm*
  • 0 over 7 years ago
    Yes, you are correct, but I am working with a very large customer with over 500k products that have long names, and over 1m users. Making it default to the way they are searching in their legacy product (that 1IM is replacing), will remove another training headache.
  • 0 over 7 years ago
    Hi Craig,
    please refer to the manual:
    support.oneidentity.com/.../5
    Regards,
    Geraldine
  • 0 over 7 years ago
    Thanks Geraldine. I have reviewed the document that you linked and, unless I am missing something, I don't think it is actually working as described. For example, one of the examples of a search criteria was:
    Search: John OR Doe
    Result: Finds Jane Doe and John Donut

    That would mean each of those Search criteria, John or Doe would be a wildcard search since the "Doe" returned Jane Doe.

    In our system, the default search method is searchcriteria*. So, if we use just "Doe", the search would return nothing.

    What is described is what we want as for "Doe" to return Jane Doe, it would have to be a "contains" search (*Doe*).

    Hope all this makes sense,
    Craig
  • 0 over 7 years ago

    Hi Craig,

    first of all, can you check if the following configuration parameter is turned on Common\Indexing\IndexNonTokenChars?

    And for the explanation. You have to keep in mind that an index search based on tokens (like a google search or several others) work differently compared with a SQL like search.

    In the examples, John and Doe are tokens and can be matched directly and will only be matched if the token can be matched exactly. This has nothing to do with a wildcard search. John OR Doe means that all entries will be returned that match either with the token John or the token Doe. No wildcard search involved here.

    But back to your case. The default setting ensures that a search for Doe will not be an exact search as "Doe" would ensure but the search will be for Doe* so that entries like Does OR Doerdel will be found as well. Remember, the token for Doerdel is Doerdel and not Doe.

    And in regards to your *contains* search. If we would activate this ootb, the customer would lose the ability to present the search results while you type.