# Increase Validation Rules Functionality

**URL:** <https://community.tulip.co/t/increase-validation-rules-functionality/13567>\
**Category:** Product Suggestions\
**Tags:** widget, widget-validation, number-precision\
**Created:** [January 20, 2025, 10:07pm UTC](https://community.tulip.co/t/increase-validation-rules-functionality/13567 "2025-01-20T22:07:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ktoole](https://avatars.discourse-cdn.com/v4/letter/k/b9bd4f/32.png) [@ktoole](https://community.tulip.co/u/ktoole)\
**Post date:** [January 20, 2025, 10:07pm UTC](https://community.tulip.co/t/increase-validation-rules-functionality/13567/1 "2025-01-20T22:07:42Z")

</div>

It would be great to have the ability to specify things about the input we’re validating. Eg. a number input needing to be 6 digits. Specifying things almost like a regex to test that stuff natively before a trigger is ever run.

Also on the enabled state side allowing us to select multiple variables as required for enabling, without having to write an unwieldy expression.

---

<div class="post-metadata">

**Author:** ![OlgaStroilova](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/olgastroilova/32/7199_2.png) [@OlgaStroilova](https://community.tulip.co/u/OlgaStroilova)\
**Post date:** [January 21, 2025, 12:07am UTC](https://community.tulip.co/t/increase-validation-rules-functionality/13567/2 "2025-01-21T00:07:11Z")

</div>

Hi @ktoole ,

Great timing – We’re actually working on a new validation rule for Numbers Inputs now, that lets the App Builder specify the number of digits after the decimal. We’ll be sharing this out shortly!

Could you share a bit more about the enabled state multiple variable request? What kind of logic are you writing now? A screenshot or link to your app would be helpful.

- Olga

---

<div class="post-metadata">

**Author:** ![OlgaStroilova](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/olgastroilova/32/7199_2.png) [@OlgaStroilova](https://community.tulip.co/u/OlgaStroilova)\
**Post date:** [January 29, 2025, 5:20pm UTC](https://community.tulip.co/t/increase-validation-rules-functionality/13567/3 "2025-01-29T17:20:03Z")

</div>

Great news - we’re working on a decimal place validation rule:

> [@Upcoming Release: Numbers Precision](https://community.tulip.co/t/upcoming-release-numbers-precision/13644):
>
> Dear Tulip Contributors, Great news - We’re excited to announce a much-requested platform update to how we store and preserve numeric data, which we’ll start rolling out as of r306/early February. Details – We’re updating how numbers are represented in Tulip Tables and Completions to support capturing, storing, and displaying trailing zeros, for example, 1.20 versus 1.2. Number data, previously stored in our Postgres database as type [Float](https://www.postgresql.org/docs/current/datatype-numeric.html#DATATYPE-FLOAT), will be stored, moving forward, as a different type …