# \[DONE\] Ability to Set Form as Default New Button **URL:** \ **Category:** Ideas & Features\ **Tags:** form-view\ **Created:** [February 18, 2023, 2:22pm UTC](https://community.fibery.io/t/done-ability-to-set-form-as-default-new-button/4016 "2023-02-18T14:22:36Z")\ **Posts on this page:** 1\ **Showing post:** 6
**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:** [September 22, 2023, 6:28am UTC](https://community.fibery.io/t/done-ability-to-set-form-as-default-new-button/4016/6 "2023-09-22T06:28:14Z")
> [@danielbmarsh](#): > > My guess is that he doesn’t want to use the table on the database view. I get that he doesn’t want to use ‘database view’ (for whatever reason) but I don’t understand what this has to do with how a form works. There are loads of places where you can create an entity without using the db view, so I would say that db view is ‘avoidable’ irrespective of what you do with forms. but nevermind. 🤷 From his and your posts, is it correctly understood that you want to limit creation of an entity to always being achieved via a form? And is this basically a way of achieving ‘required fields’ on entity creation? We don’t currently have a nice way of making fields mandatory in all places where entity creation can occur, but I can see some other related topics: > [@\[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). > [@Creating "Required Field" Prompts](https://community.fibery.io/t/creating-required-field-prompts/2098): > > Just learned how to add these “Required Field” prompts. See example here: Video Source: [In Focus Project Planning - Part 2 | TrueBrow Use Case - YouTube](https://youtu.be/ESxS5Zib6lk?t=222) Will update this post again but feel free to add the steps below slight_smile > [@How to increase quality of the created tickets?](https://community.fibery.io/t/how-to-increase-quality-of-the-created-tickets/2662): > > In the implementation I use now, currently, there is ability to create instantly e.g. features or bugs or other database entities. Leads to a lot of “one liners” because there is no such things as “create form”. I am looking into the ways to make creators fill in some mandatory hygienic attributes. What are the ways to make this happen? I see that buttons can be created, but then I would need to prevent everything created via other channels (e.g. lists of boards)? I am looking for an answer … It is possible that the solution to the ‘required fields’ problem might be enforcing specific form view usage, but there might be other ways it could be solved. --- _[View the full topic](https://community.fibery.io/t/done-ability-to-set-form-as-default-new-button/4016)._