Default value for new instances

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.

2 Likes

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

3 Likes

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

1 Like

+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.

1 Like

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?

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

1 Like

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.

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 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.

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.

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.

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)

Thank you for this. I may have forgotten I could do validation rules on creation now. Very useful feature!