# Default value for new instances
**URL:** https://community.fibery.io/t/default-value-for-new-instances/266
**Category:** Ideas & Features
**Created:** [June 28, 2019, 9:19am UTC](https://community.fibery.io/t/default-value-for-new-instances/266 "2019-06-28T09:19:03Z")
**Posts on this page:** 15
**Page:** 1
### Author:  [@Jorge](https://community.fibery.io/u/Jorge)
#### Post date: [June 28, 2019, 9:19am UTC](https://community.fibery.io/t/default-value-for-new-instances/266/1 "2019-06-28T09:19:03Z")
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 entry I have to remember to select myself in a custom field.
---
### Author:  [@mdubakov](https://community.fibery.io/u/mdubakov)
#### Post date: [June 28, 2019, 10:14am UTC](https://community.fibery.io/t/default-value-for-new-instances/266/2 "2019-06-28T10:14:05Z")
@Jorge So far you can assign default values for Single Select only. We are going to expand this option to all fields in future.
---
### Author:  [@Pagandai\_V\_Pannirsel](https://community.fibery.io/u/Pagandai_V_Pannirsel)
#### Post date: [August 14, 2019, 11:14pm UTC](https://community.fibery.io/t/default-value-for-new-instances/266/3 "2019-08-14T23:14:52Z")
It would be more userfriendly to make data entry tables simplified form with defaults valuesalong with this request made here
---
### Author:  [@helloitse](https://community.fibery.io/u/helloitse)
#### Post date: [December 7, 2024, 8:51pm UTC](https://community.fibery.io/t/default-value-for-new-instances/266/4 "2024-12-07T20:51:26Z")
+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.
---
### Author:  [@Eva\_Folch](https://community.fibery.io/u/Eva_Folch)
#### Post date: [August 27, 2025, 10:25am UTC](https://community.fibery.io/t/default-value-for-new-instances/266/5 "2025-08-27T10:25:51Z")
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.
---
### Author:  [@danielbmarsh](https://community.fibery.io/u/danielbmarsh)
#### Post date: [August 27, 2025, 1:13pm UTC](https://community.fibery.io/t/default-value-for-new-instances/266/6 "2025-08-27T13:13:08Z")
Any chance this will be dynamic, meaning you can set the default value based on a formula?
---
### Author:  [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)
#### Post date: [August 27, 2025, 3:45pm UTC](https://community.fibery.io/t/default-value-for-new-instances/266/7 "2025-08-27T15:45:23Z")
Once this feature is prioritized, it will work like you described 🙂
---
### Author:  [@Bronn](https://community.fibery.io/u/Bronn)
#### Post date: [March 18, 2026, 4:52pm UTC](https://community.fibery.io/t/default-value-for-new-instances/266/8 "2026-03-18T16:52:10Z")
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 fill it in, only for it to be updated immediately after, but I don’t see any other way around this.
---
### Author:  [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [March 18, 2026, 5:02pm UTC](https://community.fibery.io/t/default-value-for-new-instances/266/9 "2026-03-18T17:02:50Z")
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
---
### Author:  [@Bronn](https://community.fibery.io/u/Bronn)
#### Post date: [March 18, 2026, 5:07pm UTC](https://community.fibery.io/t/default-value-for-new-instances/266/10 "2026-03-18T17:07:42Z")
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 and spend time trying to look it up, only for it to update automatically anyway.
I can put a note in the tooltip and do training, but realistically, users won’t read the tooltip every time and may add expenses infrequently enough that they forget the training.
I’m just trying to make things as simple as possible for end users.
---
### Author:  [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [March 18, 2026, 5:10pm UTC](https://community.fibery.io/t/default-value-for-new-instances/266/11 "2026-03-18T17:10:08Z")
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.
---
### Author:  [@Bronn](https://community.fibery.io/u/Bronn)
#### Post date: [March 18, 2026, 5:13pm UTC](https://community.fibery.io/t/default-value-for-new-instances/266/12 "2026-03-18T17:13:14Z")
My issue is on the initial creation though. How do I get the user to fill in the Cost field ONLY if the Expense Category does not have a defined Cost?
I’m aware I can filter to run automations and validation rules once it’s created.
---
### Author:  [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [March 18, 2026, 9:35pm UTC](https://community.fibery.io/t/default-value-for-new-instances/266/14 "2026-03-18T21:35:23Z")
Here’s a sample space that I think achieves what you need, namely:
- if an expense is created in (or linked to) a category with fixed cost, then the cost will be automatically set to that value
- a user cannot update the expense cost to anything else if the category cost is fixed
- a user needs to provide a cost value if the category doesn’t have one
- it is not possible to clear the cost field value in any case
`https://shared.fibery.io/t/69a6430e-5d0a-4846-8ceb-4ee0d3b59800-expense-management`
(pasted as a code block because discourse messes up sharing urls)
---
### Author:  [@Bronn](https://community.fibery.io/u/Bronn)
#### Post date: [March 23, 2026, 2:08pm UTC](https://community.fibery.io/t/default-value-for-new-instances/266/15 "2026-03-23T14:08:56Z")
Thank you for this. I may have forgotten I could do validation rules on creation now. Very useful feature!
---
### Author:  [@mdubakov](https://community.fibery.io/u/mdubakov)
#### Post date: [June 25, 2026, 12:59pm UTC](https://community.fibery.io/t/default-value-for-new-instances/266/16 "2026-06-25T12:59:33Z")
Now you can set default values for basic fields
> [@June 25, 2026 / brick Custom Apps, AI credits & extra usage, Better performance for large tables, Set static default values for basic fields, Automations history](https://community.fibery.io/t/june-25-2026-custom-apps-ai-credits-extra-usage-better-performance-for-large-tables-set-static-default-values-for-basic-fields-automations-history/11012?sort=top):
>
> Yesterday we had a [very long degraded performance incident](https://status.fibery.io/cmqrvsgt200dt2io3o9dg756z) for integrations, reports and automations. We still didn’t identify the root cause (and even AI feels helpless here). The incident has nothing to do with today’s release, but if things will go south again, blame the heatwave hot_face and MongoDB. Custom Apps (experimental) Fibery now lets you build your own Apps — custom, client-side UI that runs on top of your workspace data. Now any user can build custom solutions tailored for speci…