# \[DONE\] Required fields

**URL:** <https://community.fibery.io/t/done-required-fields/2011>\
**Category:** Ideas & Features\
**Created:** [September 13, 2021, 12:30pm UTC](https://community.fibery.io/t/done-required-fields/2011 "2021-09-13T12:30:53Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [February 4, 2025, 9:45am UTC](https://community.fibery.io/t/done-required-fields/2011/22 "2025-02-04T09:45:35Z")

</div>

Implementation is in progress

![2025-02-04 11.44.56](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/09c32c928ebd2148d4eb8366df583eb4449bf55f.gif)

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [February 20, 2025, 12:39pm UTC](https://community.fibery.io/t/done-required-fields/2011/23 "2025-02-20T12:39:42Z")

</div>

Released today. In the next releases we will make UI less obtrusive in all views

> [@February 20, 2025 / police\_officer Required Fields, Comments on Whiteboards, Asana integration, some permissions improvements](https://community.fibery.io/t/february-20-2025-required-fields-comments-on-whiteboards-asana-integration-some-permissions-improvements/8290):
>
> This release is packed with several highly-anticipated features, including required fields and whiteboard comments. policeman Required Fields Sometimes you need to enforce mandatory fields to ensure data consistency and integrity when creating or updating entities. Now you can do it via Required fields option in the Advanced section of Field setup. You can require a value option for almost all fields, including: Basic Text, URL, Email, Phone, Number, Date, Single Select, Parent relation (man…

---

<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:** [February 20, 2025, 1:53pm UTC](https://community.fibery.io/t/done-required-fields/2011/24 "2025-02-20T13:53:12Z")

</div>

Closed on February 20, 2025, 1:53pm UTC



---

<div class="post-metadata">

**Author:** ![Francisco\_Barros](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/francisco_barros/32/8026_2.png) [@Francisco\_Barros](https://community.fibery.io/u/Francisco_Barros)\
**Post date:** [October 4, 2024, 7:47pm UTC](https://community.fibery.io/t/done-required-fields/2011/25 "2024-10-04T19:47:42Z")

</div>

I’m just now starting to actually use Fibery. From what I’ve searched in the documentation and on this forum, if I’m not mistaken, it’s not possible to indicate that a database field is mandatory.

So, I’d like to know, if possible, how this situation has been overcome, in other words, how to force a user (“internal”, and not an external user/forms) to fill in a field when inserting a new entity.

Thank you very much!

---

<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:** [October 4, 2024, 8:09pm UTC](https://community.fibery.io/t/done-required-fields/2011/26 "2024-10-04T20:09:48Z")

</div>

It is not possible, but feel free to vote for it

> [@\[DONE\] Required fields](https://community.fibery.io/t/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).

[Previous page](https://community.fibery.io/t/done-required-fields/2011.md?page=1)