Contacts starting with letter 'D' throw a too many results error

(0) Share

Report

Posted on by Community Member

Whenever I try and assign a contact to a Case that starts with the letter 'D' I am getting the following error. This is only happening with D for now.

"There are more search results than can be displayed. Try adding more search terms (such as last name) to narrow your results."

I've confirmed this customer does have a Contact starting with the letter D

I did some quick googling and it sounds like the field can only lookup 10,000 records for a Contact. However I searched in SQL and am only seeing 7,000 if I include first and last names.

SELECT *
  FROM [MSCRM].[dbo].[ContactBase]
  WHERE FirstName Like 'D%'
  OR LastName Like 'D%'

Is it looking in more than first and last name?  How can I resolve this/find out whats causing the issue so I can clean the data up.

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (1)

Suggested answer

ScottDurow 21 on at

Like (0)

Report

It could be that you have other columns in your quick find columns on contact so that is giving you more than 10,000.

You could disable quick find record limits in settings if you really need to - but I think you'd be better of asking users to restrict the search more - or adding a pre search filter to restrict the records - www.magnetismsolutions.com/.../crm-2013-javascript-lookup-filtering-using-addcustomfilter

Hope this helps

Was this reply helpful? Yes No
BadrinathB 970 on at

Like (0)

Report

Which version of CRM are you using? I think range in 5K in 2013.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

Open the Quick Find view for Contacts and look at the Find Columns to see which fields are being searched. From memory, OOB fields include email address which is often useful to catch people known by a short name starting with different letters (eg Bob has email address Robert.Smith@...). But this won't add many to your query since most people have their first name or initial or last name as the start of their email address, so I would leave that one.

I think the culprit here is Company (Parent Customer). OOB this is a search field for Contacts, so if you search for "Acme" you find all Contacts who work for any customer with a name begining "Acme". Personally I find lots of my clients find this frustrating. If they type a company name in, especially if they type all of it exactly correct, then hit TAB, CRM asks "Did you maybe mean these people?" and they get annoyed because it did not just use what they typed. So this is one that I often remove anyway, so if someone wants a person they type a person's name, if they want a company, they type that.

I think in your case this would definitely start to stretch the limits, if you think of all Contacts begining with D and all contacts who work at any company begining with D, added together.

Also look out for things like City, which is not a great field to have in the search, unless people will actually type a whole city name, but I expect more false positives off that than useful data. Doubly bad since City comes from Address entity, so it has to use a join.

But anyway, what kind of users type just "D" and expect to get any kind of useful results that they can select from, in a database that large? Surely two or three characters would not kill them? Maybe the error message is a good thing!

Was this reply helpful? Yes No