# \[DONE\] Phone number field/extension

**URL:** <https://community.fibery.io/t/done-phone-number-field-extension/439>\
**Category:** Ideas & Features\
**Tags:** flexible-domain\
**Created:** [December 2, 2019, 3:54am UTC](https://community.fibery.io/t/done-phone-number-field-extension/439 "2019-12-02T03:54:33Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\
**Post date:** [November 11, 2021, 11:15pm UTC](https://community.fibery.io/t/done-phone-number-field-extension/439/13 "2021-11-11T23:15:40Z")

</div>

@mdubakov and the team thank you for implementing this 😁

I had two questions:

**1. Validation**

> [@CHANGELOG: Nov 10 / New Terms (App → Space, Type → Database), New Space Editor, Actions in Headers in Table View, Phone field](https://community.fibery.io/t/changelog-nov-10-new-terms-app-space-type-database-new-space-editor-actions-in-headers-in-table-view-phone-field/2202/1):
>
> Note that this field has no validation, so you can put anything you want here

Is validation going to be on the list of future improvements for this type or was this a deliberate choice? I saw in various places that validation is generally something that the team will be working on, but thought I should ask in regards to this specifically. I imagine validation is going to be quite helpful if/when we are also able to have external facing form-views (contacts, sales, CRM, etc.)

**2. Field Conversion**

Is there a process for converting existing text field to phone field? I’ve used a button to populate a new phone field with previous text data, but as new field types become available, it is really helpful to be able to just convert types.

---

_[View the full topic](https://community.fibery.io/t/done-phone-number-field-extension/439)._
