# Numeric Bounds Checking

**URL:** <https://forum.inductiveautomation.com/t/numeric-bounds-checking/7138>\
**Category:** Ignition\
**Created:** [August 23, 2013, 5:34pm UTC](https://forum.inductiveautomation.com/t/numeric-bounds-checking/7138 "2013-08-23T17:34:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![phassler](https://avatars.discourse-cdn.com/v4/letter/p/5f8ce5/32.png) [@phassler](https://forum.inductiveautomation.com/u/phassler)\
**Post date:** [August 23, 2013, 5:34pm UTC](https://forum.inductiveautomation.com/t/numeric-bounds-checking/7138/1 "2013-08-23T17:34:59Z")

</div>

Bounds checking rejects a valid entry after an invalid one. If you make a new numeric text field, accept all of the default settings except: turn on “Use Bound?”, turn on “Error on Out-of-bounds”, set “number type” to float. The minimum and maximum defaults of 0 and 100 are OK. Then go into run /preview mode. Type a valid number (2.3), it is accepted. Now type an out of range number (-5.6), an error is posted and the value reverts to 2.3 - so far so good. Now type another valid number (7.6), the value reverts to the previous value (2.3) (THIS IS THE BUG). Now type another valid number (8.3), it is accepted.

In summary, after entering an invalid number, you need to enter a valid number twice

---

<div class="post-metadata">

**Author:** ![James.Lorenz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/james.lorenz/32/3290_2.png) [@James.Lorenz](https://forum.inductiveautomation.com/u/James.Lorenz)\
**Post date:** [August 23, 2013, 6:41pm UTC](https://forum.inductiveautomation.com/t/numeric-bounds-checking/7138/2 "2013-08-23T18:41:31Z")

</div>

Thanks for the report, I was able to replicate and I will file a bug ticket.

---

<div class="post-metadata">

**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\
**Post date:** [October 14, 2013, 6:43pm UTC](https://forum.inductiveautomation.com/t/numeric-bounds-checking/7138/3 "2013-10-14T18:43:33Z")

</div>

This has been fixed and should be in 7.6.4-rc3

Best,