There seems to be a glitch when searching for phone numbers. If the phone number has dashes in it, the search. Here are the 2 examples:
select * from vwCONTACTS_List where 1 = 1 and ( NAME like '%2077754363%' escape '\' ) or ( ACCOUNT_NAME like '%2077754363%' escape '\' ) or ( ASSISTANT like '%2077754363%' escape '\' ) or ( EMAIL1 like '%2077754363%' escape '\' ) or ( EMAIL2 like '%2077754363%' escape '\' ) or ( PHONE_HOME like '%2077754363%' escape '\' ) or ( PHONE_MOBILE like '%2077754363%' escape '\' ) or ( PHONE_WORK like '%2077754363%' escape '\' ) or ( PHONE_OTHER like '%2077754363%' escape '\' ) or ( PHONE_FAX like '%2077754363%' escape '\' ) or ( ASSISTANT_PHONE like '%2077754363%' escape '\'select * from vwCONTACTS_List where 1 = 1 and ( NAME like '%207-775-4363%' escape '\' ) or ( ACCOUNT_NAME like '%207-775-4363%' escape '\' ) or ( ASSISTANT like '%207-775-4363%' escape '\' ) or ( EMAIL1 like '%207-775-4363%' escape '\' ) or ( EMAIL2 like '%207-775-4363%' escape '\')
Notice how the one with Dashes never even looks in the phone field
The problem is that we are trying to distinguish between a search that contains numbers and one that contains text. In ~/Contacts/SearchContacts.ascx.cs, we use Information.IsNumeric() to determine if we should search phone numbers. In retrospect, this seems inadequate.
You can just remove the if ( Information.IsNumeric(sUnifiedSearch) ) condition.
OK, we can modify this.
Do you plan on modifying the base code? We try to minimize custom modifications to keep upgrades easy.
In this case, I hope you will agree phone numbers are numeric and are the perfect candidate to search a contact record phone field.
If the input mask allows dashes then the search should also return the input value.
Thanks for such a quick reply.
