6
Mandatory Fields
Source: twentyhq/twenty#14186 · opened by @kyrpav
Scope & Context
It would be great to be able to define per model Mandatory Fields
Current behavior
There is no possibility to mark a field in a model as mandatory. Which allows users to create problematic records.
It will probably make problem in the Dashboard solutions that you also have in progress.
Also from API you can create whatever records just by adding the name field also which is always there.
Expected behavior
User to be able to mark in the field edit the field as mandatory.
Also if the field is mandatory an autoincrement if it is integer.
This will have immediate impace on the API
It would be great to be able to define per model Mandatory Fields
Current behavior
There is no possibility to mark a field in a model as mandatory. Which allows users to create problematic records.
It will probably make problem in the Dashboard solutions that you also have in progress.
Also from API you can create whatever records just by adding the name field also which is always there.
Expected behavior
User to be able to mark in the field edit the field as mandatory.
Also if the field is mandatory an autoincrement if it is integer.
This will have immediate impace on the API
No pledges yet. Be the first to back this.
Comments
Similar requests
Configure mandatory fields by stage
3 votes · 0 comments
Add template library for records
3 votes · 0 comments
UX improvement : Field Groups, better visibility
4 votes · 0 comments
Question: Does conditional field visibility exist? (show/hide fields based on Select field value)
3 votes · 0 comments
System-managed fields cannot be renamed — createdAt/createdBy/updatedAt/updatedBy stay in English on every record page
1 vote · 0 comments
No comments yet.