Setting Default Field Values
You can use default field values to reduce manual entry errors and ensure that your object data remains consistent across all creation methods. The system applies the default value or expression only if a field is left blank during creation. If a user or an external API provides a value, it overrides the default. This ensures data completeness while enabling manual input when necessary. For example, a status field can default to Open, guaranteeing that all new tickets are captured by administrative filters and dashboards without requiring manual input from the user.
Defaults can be static values or generated by an expression. Use Input as Value for fixed data that remains constant for every entry, such as a default status or category. Use the Expression Builder for dynamic data that changes based on when the entry is created, such as setting a date field to the current time.
You can configure default field values or expressions for these field types:
Boolean: Ensure a binary state by defaulting to True or False.
Date: Default to a specific date or use expressions for relative dates (e.g., current date).
Numeric: Set a starting integer or decimal value.
Picklist: Select a specific option from the list to be the initial value for the field.
Text: Provide a static string for text.
Adding Default Values to Object Fields
-
Begin editing the desired custom field.
-
Go to the Advanced tab.
-
Toggle the Use Default Value switch to active.
-
Select Input as Value or Expression Builder.
The expression builder appears depending on the field type.
-
Enter the default value or expression.
-
Click Save.
Example Use Case: Automating Task Assignment
In a project management application, you can use default field values to ensure every new task is correctly categorized and timestamped immediately upon creation. This is particularly useful for maintaining clean dashboards and ensuring data integrity across both the UI and headless APIs.
To achieve this, configure the following defaults in the task object:
-
Standardizing Initial Status: Set the Status picklist field to a default value of
Backlog. This ensures new tasks appear in “To Do” filters without requiring manual input from the creator. -
Automating Timestamps: Use the expression builder to set the Submission Date field to
currentDate. This provides an immutable record of when the task entered the system.
By implementing default field values, you ensure that every object entry starts with a reliable data set, regardless of how it was created. To further protect your data integrity, consider combining default field values with read-only fields. This enables you to set a system-generated default that users can see but cannot manually overwrite, ensuring your business logic remains secure.