In Dynamics CRM 3.0, the Look For box is supposed to honor the Find Columns
settings specified in the Quick Find View.

This appears to work for Accounts and Contacts, but does behave the same way
for Leads and Cases. For example, try searching for the numeric portion of a
case number with Case Number, Case Description and Title specified as the
Quick Find columns.

I can't find this behavior documented anywhere and the current user
experience differs from what I can find in the docs. Does anyone know what's
really happening behind the scenes?

--
Bob McMahon
Sr. Business Systems Manager
Roland DGA Corporation

RE: Odd behavior of Look For feature by MattNC

MattNC
Thu Sep 07 19:32:02 CDT 2006

Bob: I responded to your similar comment on my blog, but thought I'd post it
here for others to see as well. The Look For functionality does indeed work
for leads and cases, and if it's not working on yours you may want to open a
support case with Microsoft. However, read on and see if this helps:

In many cases you will have to use an asterisk as a wild card in the Quick
Find. For example, when looking for a case, it's not enough to put in the
numeric portion of the case number, such as 72237. Case numbers are strings
like CAS-72237-XFGHY. The Quick Find looks for field values that begin with
whatever you type in. So instead, you might type in *72237 and you will get a
list of all cases that have that number in one of the quick find fields.

It's the same with leads, I suspect. By default I think the leads quick find
search for values in the fullname field that begin with whatever you type. So
if you have Frank Johnson as a lead, and you type Johnson, you won't get any
results. However, if you use the wild card, and type *John you will get all
leads with john in them, such as John Smith, Frank Johnson or Bill Littlejohn.


--
Matt Wittemann, CRM MVP
http://icu-mscrm.blogspot.com


"Bob McMahon" wrote:

> In Dynamics CRM 3.0, the Look For box is supposed to honor the Find Columns
> settings specified in the Quick Find View.
>
> This appears to work for Accounts and Contacts, but does behave the same way
> for Leads and Cases. For example, try searching for the numeric portion of a
> case number with Case Number, Case Description and Title specified as the
> Quick Find columns.
>
> I can't find this behavior documented anywhere and the current user
> experience differs from what I can find in the docs. Does anyone know what's
> really happening behind the scenes?
>
> --
> Bob McMahon
> Sr. Business Systems Manager
> Roland DGA Corporation

RE: Odd behavior of Look For feature by bmcmahon

bmcmahon
Fri Sep 08 11:16:03 CDT 2006

Thanks, Matt!

I tried the wild card characters in the class (on cases) but found no
results. Today, it appears to be working. After some additional checking I
think I figured out the confusion.

Quick find only works on ACTIVE records. The case we were looking for
yesterday was resolved. Changing the view from Active to All does not affect
the Quick Find. Quick Find will always revert back to searching for active
records.

While I can explain this behavior, I'm a bit torn on the usability aspects
of this. Most users do not like to fiddle with Advanced Find when they are
looking for one particular record. Quick Find should be able to handle that
scenario.

Advanced Find, in 3.0, has been extended with some very nice features and a
load of power, but this came at the expense of the simple search. Now, to
look for a closed case, or closed lead, the user is forced to navigate
through Advanced Find. This is likely to result in each user creating their
own "simple search" variations. If Quick Find would honor the view that is
active, all these private views could be averted. I believe there is a
feature request already fined on this.

Thanks again for the quick response!

--
Bob McMahon
Sr. Business Systems Manager
Roland DGA Corporation


"MattNC" wrote:

> Bob: I responded to your similar comment on my blog, but thought I'd post it
> here for others to see as well. The Look For functionality does indeed work
> for leads and cases, and if it's not working on yours you may want to open a
> support case with Microsoft. However, read on and see if this helps:
>
> In many cases you will have to use an asterisk as a wild card in the Quick
> Find. For example, when looking for a case, it's not enough to put in the
> numeric portion of the case number, such as 72237. Case numbers are strings
> like CAS-72237-XFGHY. The Quick Find looks for field values that begin with
> whatever you type in. So instead, you might type in *72237 and you will get a
> list of all cases that have that number in one of the quick find fields.
>
> It's the same with leads, I suspect. By default I think the leads quick find
> search for values in the fullname field that begin with whatever you type. So
> if you have Frank Johnson as a lead, and you type Johnson, you won't get any
> results. However, if you use the wild card, and type *John you will get all
> leads with john in them, such as John Smith, Frank Johnson or Bill Littlejohn.
>
>
> --
> Matt Wittemann, CRM MVP
> http://icu-mscrm.blogspot.com
>
>
> "Bob McMahon" wrote:
>
> > In Dynamics CRM 3.0, the Look For box is supposed to honor the Find Columns
> > settings specified in the Quick Find View.
> >
> > This appears to work for Accounts and Contacts, but does behave the same way
> > for Leads and Cases. For example, try searching for the numeric portion of a
> > case number with Case Number, Case Description and Title specified as the
> > Quick Find columns.
> >
> > I can't find this behavior documented anywhere and the current user
> > experience differs from what I can find in the docs. Does anyone know what's
> > really happening behind the scenes?
> >
> > --
> > Bob McMahon
> > Sr. Business Systems Manager
> > Roland DGA Corporation