Configure Required Fields in Fibery
Open a field’s Advanced settings and enable Always require a value. Fill existing blanks before enforcing the requirement and update any automated creation paths.
Before you start: Have configuration access and a supported field type. Multi-selects, many-to-many relations, formulas and lookups cannot use this requirement.
Worked example: A Feature must have a Product Area parent before planning. Making the many-to-one parent required prevents orphan Features; a form-only checkbox would not cover every creation path.
Step-by-step guide
Pick a necessary invariant
Choose the one field whose absence makes the record unusable. Avoid requiring speculative estimates just to make the database appear complete.
Enable the native rule
In Database → Fields open Product Area, expand Advanced and turn on Always require a value.
Resolve existing blanks
Supply appropriate values for existing entities as prompted. Review the affected set rather than assigning a misleading default to every old Feature.
Check record creation
Create a sample Feature from a Table or another entry point. Confirm creation asks for the parent and that the field is marked as required.
Update automated writes
Review API and automation actions that create Features. Provide the required parent in those paths and verify they succeed.
Common mistakes
Confusing Form-required with field-required
A form-only requirement is not the same as a database rule. Quick creation inside related forms follows field-level requirements.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.