# 🆕 Number entry validation now possible

**URL:** <https://community.glideapps.com/t/number-entry-validation-now-possible/13674>\
**Category:** Community Resources\
**Created:** [August 7, 2020, 4:58am UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674 "2020-08-07T04:58:42Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [August 7, 2020, 4:58am UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/1 "2020-08-07T04:58:42Z")

</div>

![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/2/2f4bd9beabe9b49d4ab8eefee14004ca47b65e95.png)

Number entry component now allows you to specify a min value and max value for validation.

If the user enters a value that’s not in the range, they will get a warning that’s specific to the range you provided.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/6/6e005b2e4330d5ea765a2dda96d37a4f2fdfb960.png)

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/3/3f3b2e3f300965e2bf3bd455f5fae7a1aa55b39e.png)

---

<div class="post-metadata">

**Author:** ![Rasha](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rasha/32/4585_2.png) [@Rasha](https://community.glideapps.com/u/Rasha)\
**Post date:** [August 7, 2020, 6:27am UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/2 "2020-08-07T06:27:53Z")

</div>

Thought maybe that could preserve a 5-digit entry that starts with Zero if min/max is set to 5 — no luck. Still shaves the first zero 😤

---

<div class="post-metadata">

**Author:** ![V88](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/v88/32/90054_2.png) [@V88](https://community.glideapps.com/u/V88)\
**Post date:** [August 7, 2020, 9:07am UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/3 "2020-08-07T09:07:12Z")

</div>

Gonna be one of those “love Team Glide” days …

---

<div class="post-metadata">

**Author:** ![V88](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/v88/32/90054_2.png) [@V88](https://community.glideapps.com/u/V88)\
**Post date:** [August 7, 2020, 9:11am UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/4 "2020-08-07T09:11:24Z")

</div>

Now @Mark how about an optional RegEx for text entry … come on … you know you love it?

---

<div class="post-metadata">

**Author:** ![Gabriel\_Sobral](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gabriel_sobral/32/6513_2.png) [@Gabriel\_Sobral](https://community.glideapps.com/u/Gabriel_Sobral)\
**Post date:** [August 7, 2020, 12:39pm UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/5 "2020-08-07T12:39:34Z")

</div>

> [@V88](#):
>
> Now @Mark how about an optional RegEx for text entry … come on … you know you love it?

This would be mind-blowing 🤯

---

<div class="post-metadata">

**Author:** ![McJagger](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mcjagger/32/18616_2.png) [@McJagger](https://community.glideapps.com/u/McJagger)\
**Post date:** [August 7, 2020, 1:51pm UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/6 "2020-08-07T13:51:39Z")

</div>

I agree, the zip code entry is still an issue 😕

---

<div class="post-metadata">

**Author:** ![\_eric](https://avatars.discourse-cdn.com/v4/letter/_/5f9b8f/32.png) [@\_eric](https://community.glideapps.com/u/_eric)\
**Post date:** [August 7, 2020, 2:32pm UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/7 "2020-08-07T14:32:21Z")

</div>

Is it possible to bound the minimum and maximum values from a field in the database? It looks like it is possible from the initial image but on my screen its setup differently. It doesn’t give me that option.

 ![number entry](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/c/c78c2ac78e54666a5de2a753a785dc1f838064c7.jpeg)

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [August 7, 2020, 2:38pm UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/8 "2020-08-07T14:38:02Z")

</div>

![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/f/fc2642b0efa86db5d5df5168a8ae295f4f0670a9.png)

I can choose it, Eric.

---

<div class="post-metadata">

**Author:** ![\_eric](https://avatars.discourse-cdn.com/v4/letter/_/5f9b8f/32.png) [@\_eric](https://community.glideapps.com/u/_eric)\
**Post date:** [August 7, 2020, 2:41pm UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/9 "2020-08-07T14:41:40Z")

</div>

@ThinhDinh Yes, I see that. Its so strange because I saw it on your image but its not listed as an option on my UI.

On my UI all I get are these up and down arrows to increase or decrease the quantity.

---

<div class="post-metadata">

**Author:** ![V88](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/v88/32/90054_2.png) [@V88](https://community.glideapps.com/u/V88)\
**Post date:** [August 7, 2020, 3:01pm UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/10 "2020-08-07T15:01:39Z")

</div>

RegEx would sort that too … just saying

---

<div class="post-metadata">

**Author:** ![Gabriel\_Sobral](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gabriel_sobral/32/6513_2.png) [@Gabriel\_Sobral](https://community.glideapps.com/u/Gabriel_Sobral)\
**Post date:** [August 7, 2020, 3:06pm UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/11 "2020-08-07T15:06:40Z")

</div>

In addition to RegEx implementation, it’d be great to see a “Validation Error” message field.  
That way we could customize the validation as well the warning for the mismatch.

---

<div class="post-metadata">

**Author:** ![V88](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/v88/32/90054_2.png) [@V88](https://community.glideapps.com/u/V88)\
**Post date:** [August 7, 2020, 3:09pm UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/12 "2020-08-07T15:09:19Z")

</div>

That would allow Glide to be used in so many more scenarios

---

<div class="post-metadata">

**Author:** ![RobertoMardini](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robertomardini/32/7831_2.png) [@RobertoMardini](https://community.glideapps.com/u/RobertoMardini)\
**Post date:** [August 7, 2020, 9:17pm UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/13 "2020-08-07T21:17:23Z")

</div>

great, I hope they do the same with text input, max and min characters, to avoid people type long or short text

---

<div class="post-metadata">

**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\
**Post date:** [August 8, 2020, 11:36am UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/14 "2020-08-08T11:36:40Z")

</div>

Oh, thank you Jesus!

---

<div class="post-metadata">

**Author:** ![S\_C](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/s_c/32/12766_2.png) [@S\_C](https://community.glideapps.com/u/S_C)\
**Post date:** [August 8, 2020, 1:01pm UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/15 "2020-08-08T13:01:17Z")

</div>

🤣

---

<div class="post-metadata">

**Author:** ![Jonathon\_Kohn](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jonathon_kohn/32/8593_2.png) [@Jonathon\_Kohn](https://community.glideapps.com/u/Jonathon_Kohn)\
**Post date:** [August 9, 2020, 3:34am UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/16 "2020-08-09T03:34:07Z")

</div>

Is there currently a way to force someone to enter 10 digits? (Phone number + area code?)

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [August 9, 2020, 4:40am UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/17 "2020-08-09T04:40:54Z")

</div>

We might have a problem with the whole thing starts with one zero or many leading zeros, but if it doesn’t, I assume you can force it by letting the min be 10000000000 (1 & 9 zeros), max be 9999999999 (10 nines)

---

<div class="post-metadata">

**Author:** ![gvalero](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gvalero/32/1037_2.png) [@gvalero](https://community.glideapps.com/u/gvalero)\
**Post date:** [August 10, 2020, 6:09pm UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/18 "2020-08-10T18:09:31Z")

</div>

Hi,

Why do Min and Max values work as warning signals only instead of blocking/rejecting wrong values?

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/9/99a7c4c9a9f353b282c917f5c466f2d2f81d80f8.jpeg)

If a user writes an invalid value out of range (my case is from 1-10), this must be rejected but after 3-4 sec, the value is still appearing on screen and APP uses it without problem, it’s wrong!

Is it a bug or it was its working design? @Mark

Saludos muchachos!

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [August 10, 2020, 6:17pm UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/19 "2020-08-10T18:17:36Z")

</div>

I imagine it makes more sense in a form, where the submit button won’t work until you enter a value in range. But I suppose in a detail view screen, it’s only a warning? Since entry components on a view screen write directly to the sheet in real time, are you expecting it to clear out if the value is outside of the range?

---

<div class="post-metadata">

**Author:** ![gvalero](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gvalero/32/1037_2.png) [@gvalero](https://community.glideapps.com/u/gvalero)\
**Post date:** [August 10, 2020, 6:30pm UTC](https://community.glideapps.com/t/number-entry-validation-now-possible/13674/20 "2020-08-10T18:30:35Z")

</div>

Hola Jeff,

Well, at least I hope it will disable the wrong value and APP keeps **working with last valid value** otherwise, this improvement is going to lose benefits.

In every software you have used before, _ **Min and Max values** _ means the same: only allowed values between them!

[Next page](https://community.glideapps.com/t/number-entry-validation-now-possible/13674.md?page=2)
