Skip to content

A custom checkbox field (Boolean type, with a Yes/No Enumeration) has its Default Value set to 'No' in the field's properties, but new records still show the underlying database value as Empty/NULL rather than 'No' — is there a system-wide setting to make this default actually persist to the database?

Answer

No — the field-properties Default Value only controls what's shown as a suggested value when creating a new record in the client UI; it doesn't automatically get written to the database unless a value is explicitly saved for that field (whether by the user interacting with it, or some other explicit logic setting it). There's no system-wide option to force this default to auto-persist on insert — achieving that requires a customization (such as a Persistent custom field with a PL/SQL default-value expression, or a Custom Event that explicitly sets the value on insert) rather than relying on the field-properties Default Value alone.

← Browse Platform, Aurena, and customization questions