You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user, I should be allowed to enter a phone number in the entity resolution search as space separated (123 456 789), hyphen separated (123-456-789), or without any delimiter at all (123456789). Currently I can't do that, because the phone numbers are stored in the DB with hyphens as separators.
Instead of strictly enforcing the hyphen format, maybe we should strip out the hyphens from the existing phone numbers in the DB. The app can then strip out any non-numeric characters from the user's query on the backend, and the SQL query will still return matches. This will allow for more robust searching that doesn't break if a user doesn't use the xxx-xxx-xxxx phone number format.
The text was updated successfully, but these errors were encountered:
coxjonc
changed the title
Store phone numbers as numeric digits only, no hyphens or spaces
Store phone numbers as numeric digits only, no hyphens
Mar 7, 2017
As a user, I should be allowed to enter a phone number in the entity resolution search as space separated (123 456 789), hyphen separated (123-456-789), or without any delimiter at all (123456789). Currently I can't do that, because the phone numbers are stored in the DB with hyphens as separators.
Instead of strictly enforcing the hyphen format, maybe we should strip out the hyphens from the existing phone numbers in the DB. The app can then strip out any non-numeric characters from the user's query on the backend, and the SQL query will still return matches. This will allow for more robust searching that doesn't break if a user doesn't use the xxx-xxx-xxxx phone number format.
The text was updated successfully, but these errors were encountered: