# Character length validation for number fields

**URL:** https://community.noloco.io/t/character-length-validation-for-number-fields/272
**Category:** Feature Requests
**Tags:** feature-request
**Created:** [February 13, 2024, 9:02pm UTC](https://community.noloco.io/t/character-length-validation-for-number-fields/272 "2024-02-13T21:02:00Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![buildwithjoel](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/buildwithjoel/32/1537_2.png) [@buildwithjoel](https://community.noloco.io/u/buildwithjoel)
#### Post date: [February 13, 2024, 9:02pm UTC](https://community.noloco.io/t/character-length-validation-for-number-fields/272/1 "2024-02-13T21:02:00Z")

</div>

Currently, “text length” form validation exists for text fields, but not number fields. I’d love to see a “character length” validation point for number fields.

**Use-Case Example**

 ![Screenshot 2024-02-13 at 4.00.10 PM](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/1X/d727b038dd3e7a1f39b433dcd4a767b8f2fe122f.png)

---

<div class="post-metadata">

### Author: ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)
#### Post date: [February 13, 2024, 9:35pm UTC](https://community.noloco.io/t/character-length-validation-for-number-fields/272/2 "2024-02-13T21:35:59Z")

</div>

Good suggestion Joel!

Another idea would be to turn the SSN field into a text field, and add Regex validation to it to limit it to 3 numbers

---

<div class="post-metadata">

### Author: ![buildwithjoel](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/buildwithjoel/32/1537_2.png) [@buildwithjoel](https://community.noloco.io/u/buildwithjoel)
#### Post date: [February 16, 2024, 2:07am UTC](https://community.noloco.io/t/character-length-validation-for-number-fields/272/3 "2024-02-16T02:07:08Z")

</div>

Good enough workaround for the input side of things. But for business intelligence (say an Airtable Interface displaying the data from the base used in Noloco, or a host of other platforms that might be used for a dashboard), that field will (for most platforms) still be read as a text field, so you won’t be able to build numerical metrics off of it (of course, SSN is a terrible example, but I’m thinking of other number entry fields where you might want to add some character length validation).

Long story short, good workaround – thanks for suggesting. Will still be nice though to have that validation option 🙂
