# \[DONE\] Enforce unique entries + Data validation + Required fields

**URL:** <https://community.fibery.io/t/done-enforce-unique-entries-data-validation-required-fields/7966>\
**Category:** Ideas & Features\
**Created:** [December 16, 2024, 12:01am UTC](https://community.fibery.io/t/done-enforce-unique-entries-data-validation-required-fields/7966 "2024-12-16T00:01:31Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [December 16, 2024, 7:00am UTC](https://community.fibery.io/t/done-enforce-unique-entries-data-validation-required-fields/7966/2 "2024-12-16T07:00:41Z")

</div>

Is this duplication of existing topics?

> [@\[PLANNED\] Required fields on the layout](https://community.fibery.io/t/planned-required-fields-on-the-layout/2011):
>
> We have several types, where we need to be sure some fields are not empty. It would be great if we can mark fields as required OR create a validation rule if fields are empty (display an error message).

> [@Validations / automations](https://community.fibery.io/t/validations-automations/7584):
>
> Just saw the monthly update from @mdubakov and it inspired this feature request. The required fields (above) is a good first step in what we’re missing in our workspace, which is what I would call validations. Validation is where a user is not allowed to take certain actions unless another condition is fulfilled. A few examples: Only allow updating to state “done” when “rich text” field is not empty. Only allow creating a todo if the deadline is also entered When disapproving somet…

---

_[View the full topic](https://community.fibery.io/t/done-enforce-unique-entries-data-validation-required-fields/7966)._