4.5.0.f advanced search problem

[florenceit]

advanced search of leads: search for "c" in "any email" field and it brings up all emails beginning with c correctly. search for @c
or @anydomain.com and it brings up nothing.

have a lead that changed their domain name and have a bunch of emails for them i'd like to change.
i've tried * as a wildcard as well, is that supposed to work? doesn;t look like its capable of searching substrings unless there's some other wildcard syntax Im not aware of? thanks for any help, I can look them up one at a time for now but just curious if this is a known issue or im doing something wrong.

[florenceit]

so, this is a known limitation ? any answers? thanks!

[kpit]

The wildcard character is "%" (percent symbol) by default Sugar appends the wildcard to the end of all searches so it will only find things that begin with ...

To search for a match anwhere in the field you simply put a % at the beginning of the entry. For example I want to search for all emails that have @example.com, you would type the following:

%@example.com

This will find the following:

bubba@example.com
@example.com
bogus@example.com!bad@other.com

The last example will show up because there is an automatic % placed at the end of the query that really looks like this "%@example.com%" this will translate to anywhere in the field being searched.

[sanver]

We are living in an age where people expect searches to work like Google. SugarCRM is very low on "operational efficiency" as far as search function is concerned.

Sanjay Verma
www.sanver.com
Mumbai, India

+919892481284

[mycrmspacegunnar]

We are living in an age where people expect searches to work like Google. SugarCRM is very low on "operational efficiency" as far as search function is concerned.

Sanjay Verma

Sugars search functionality is normal.
With todays SQL database technology you have two types of searches that you provide.
a) direct match or partly matchign searches
b) Fulltext searches which we close to what you are propably expecting.

That sugar per default searches with wildcard at the end makes good sense
as this pattern search can make use of indexes and is usually a magnitute faster than a search like this %somevalue%

Adding a fulltext search would certainly have some advantages, but fulltext usually starts working best only after
a big amount of text was indexed. So fulltext search is good for searching through many uploaded documents or searching in a database of some thousand websites. With the type of data that you are typically searching for in Sugar, a regular fulltext search will not always give you the expected results

What would be quite nice for Sugar would be a search which finds similar results.
There are techniques to find not only direct matching results but also similar ones.
Unrotunately most SQL databases do typically NOT provide such features out of the box.

While ist not difficult to develop a plugin for MySQL which would
add Levensthein functionality, so that Sugar could offer searches for similar matches
this will make installing Sugar much more complicated and would make portabilty to other database quite hard.


So in short the search that Sugar provides right now is what is possible with relational databases
without locking your application to one database system only.

Cheers
Gunnar

[florenceit]

as far as my concern goes just being able to use a wildcard anywhere in my search string is perfectly acceptable and should cover anything , just didn;t know that, awesome thanks!

so is % some sort of standard mysql or php search operand or was this arbitrary?

anyhow thanks this will do the trick for me!

[kpit]

The % is a standard SQL wildcard for all Databases that follow the ANSI Standard.