12-13-2012 03:41 PM
I'm curious how everyone is searching for phone numbers in SalesLogix.
Here is our scenario:
A customer calls in that we are no aware who he/she is. A salesmen types in their phone number 3334445555 into speed seach and get nothing. If you then put in (333) 444-5555 it might be able to find it but when you are on the phone with a potential client formattig the phone number as you type it is not a good enough solution.
Other options (using speed search):
1) Type in the phone number fully formatted (333) 4444-55555
2) Type in part of the number and hope there are only a few results
Other options (using lookup)
1) Seach the Contacts Main, Direct, Mobile, Home and the Accounts Main and Toll Free
Because the numbers are stored in the system formatted (xxx) xxx-xxxx it makes it hard to seach unformatted numbers.
We need a faster way to seach for all the phone numbers. Anyone have any suggestions
12-18-2012 06:15 AM
I don't know why you would, but it appears that the database is saving them formatted.
We are using the web client btw, not that it should make any difference becuase the backend core is still the same.
12-18-2012 07:54 PM
Maybe it DOES make a difference whether it's LAN or WEB (or SLXMobile). On the LAN side, you enter in the numbers only, they are formatted to look like a phone number.....and SLX stores the phone number unformatted. If you format the phone number it stores formatted. This isn't done at the SLX OLE DB Provider (or sData) Backend level, it's a function of the GUI.
I think you're on to something here......
12-19-2012 05:14 AM - edited 12-19-2012 05:22 AM
Just ran a quick test w/LAN, Mobile 2.0 (on both smartphone - droidX and tablet - Samsung 10.1)..
if you enter a "standard" number that conforms to the NANPA (North American Number Plan Admin - 10 digits) it always stores unformatted IF you do not add additional characters. If you do something like:
it will be saved that way in the db and will display that way when pulled up. Now if I do not do a +1 (just put in 603.369.3047) - it saves as 6033693047 and the display format will be (603)-369-3047
Also.. if you add an extension using "x" (ex: 6033693047x123) - it also stores unformatted and displays formatted.
If you enter less than 10 digits/characters (yes, 800FOXBORO will save as 800FOXBORO but displays as (800)-369-2676 in windows/LAN and mobile.. but as (800) 369-2676 in 8.0 web... notice the missing "-"
One thing I do find annoying is the difference in entering phone numbers on a tablet vrs my DroidX is on the droid smartphone the mobile app puts up it's own keyboard and there's no way to enter/edit an extension - BUG. - Going to disable this code in the mobility and will make the change free to anyone who wants it. NOTE: This is new to 2.0 - 1.x did not have it.
12-19-2012 06:25 AM
I just did some testing using the Web and Lan Clients (7.5.4).
When you enter 9998887777 in the lan client it saves it in the database as: 9998887777
When you enter 9998887777 in the web client it saves it in the database as: (999) 888-7777
They both display at (999) 888-7777 which is correct.
So this answers my question about why searching was goofed up. Not sure yet what we are going to do about it though...
12-19-2012 06:37 AM