It would be very useful to assign a a default value for fields and relations when defining new types. Even more interesting would be if this default value accepts some indirection like for example “Me” e.g. I was trying to model “Time Entries”. It is really simple but each time a create a new time…

@Jorge So far you can assign default values for Single Select only. We are going to expand this option to all fields in future.

It would be more userfriendly to make data entry tables simplified form with defaults valuesalong with this request made here

+1 for this. I would like to set default values for multiple field types. Most recently, a datetime field should default to the created time, but maintain it’ss ability to be changed manually.

I think this would save me a lot of automations. For example, I want the “Vat %” Column always to 19 by default, or Quantity always 1 by default, etc…since those are things I only need to change once in a while.

Any chance this will be dynamic, meaning you can set the default value based on a formula?

[image] Once this feature is prioritized, it will work like you described :slight_smile:

I am in need of the same thing. My use case is that I have a field that I need to be editable and it’s also required (say Cost on Expenses). However, if the Expense Category has a defined Cost, it will use this figure (for example, mileage is a set amount per mile). I don’t want to force someone to…

One way to address this is as follows: define an automation rule to set the value on creation and/or if the category is updated, to take the value from the expense category define a validation rule that triggers when field is updated, and blocks the change if there is an expense category linked

That’s what I was planning to do, but the category doesn’t always have a cost (if it’s variable), so I need to ensure that in those cases, the user definitely fills in the field. But I don’t want them to fill it in if the category does have a cost as I know some people will not know what the cost is…

This should still be possible using automation + validation. The automation to set the value won’t do anything if the category cost value is empty, and your validation rule can check not only that a category is linked but that the category has a non-empty cost value, as a blocker to user changes.

Default value for new instances

Ideas & Features

mdubakov June 25, 2026, 12:59pm 16

Now you can set default values for basic fields

Topic		Replies	Views
[DONE] Add Default Value for Checkbox Type Ideas & Features flexible-domain	4	561	June 25, 2026
How default values work? Get Help	10	128	February 26, 2026
Default value for People fields Ideas & Features	4	71	June 23, 2026
Allow fields in a Button User Input Form to have existing or default values prepopulated Ideas & Features automations	8	380	May 2, 2025
Create entity with button default value but allow user override Ideas & Features	2	36	September 4, 2026

Default value for new instances

Related topics