# Minimum and maximum values for number and percentage fields

**URL:** <https://community.fibery.io/t/minimum-and-maximum-values-for-number-and-percentage-fields/9298>\
**Category:** Ideas & Features\
**Created:** [July 28, 2025, 11:20pm UTC](https://community.fibery.io/t/minimum-and-maximum-values-for-number-and-percentage-fields/9298 "2025-07-28T23:20:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\
**Post date:** [July 28, 2025, 11:20pm UTC](https://community.fibery.io/t/minimum-and-maximum-values-for-number-and-percentage-fields/9298/1 "2025-07-28T23:20:13Z")

</div>

I have a use case where percentage should not be below 0 or above 100. Additionally, I would prefer to limit monetary values to positive amounts, and restrict it to a reasonable upper limit.

I know both of these headaches can be resolved with user training, but we all know how good non-technical users are at reading docs… 😬

It’d be nice to stop the situation from occurring in the first place.

---

<div class="post-metadata">

**Author:** ![danielbmarsh](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/danielbmarsh/32/13104_2.png) [@danielbmarsh](https://community.fibery.io/u/danielbmarsh)\
**Post date:** [July 29, 2025, 2:14am UTC](https://community.fibery.io/t/minimum-and-maximum-values-for-number-and-percentage-fields/9298/2 "2025-07-29T02:14:34Z")

</div>

Data validation rules would be awesome.