Phone Number Format and Import

[David Casper]

I'm working on importing users into our dev instance and am having issues with the phone numbers. They don't seem to be coming through the transform correctly, or at least how I anticipated they would.

They are coming from a CSV with E164 formatting and some have extensions. Ex: +1-828-274-9567;ext=40088

The phone number type in our DEV is the default, Phone Number (ph_number). After I run the transform the phone numbers appear as '2147483647' which apparently is the largest value an integer field can hold which confuses me since it seems the field type is a string extension? This   seems to be occurring for just about any number, with an extension or not.

I then went to my personal dev instance and change the field type to Phone Number (E164). Wen I do the import there the numbers come across correctly (+1 (828) 989-2393) UNLESS they have an extension like the above example. Then the field is left blank.

I assumed the Phone Number (E164) field type would accept E164 formatting, but there seems to be an exception. All suggestions greatly appreciated!

[Ankur Bawiskar]

Hi David,

Did you check below documentation links :

E.164 phone number field characteristics

Phone number field type

Mark Correct if this solves your issue and also hit Like and Helpful if you find my response worthy based on the impact.

Thanks

Ankur

[Michael Ritchie · Accepted solution]

I am pretty sure that field type doesn't support extensions. You will need to put that data into a separate field.

[David Casper]

@bawiskar @michael.ritchie Thanks for your guys feedback. Turned out the field type doesn't support any extension formatting so I created a new field and parsed out the extension on the SQL side. 

Thanks