# Show default value if field left empty in Button form

**URL:** <https://community.fibery.io/t/show-default-value-if-field-left-empty-in-button-form/9886>\
**Category:** Ideas & Features\
**Tags:** automations\
**Created:** [October 26, 2025, 9:57am UTC](https://community.fibery.io/t/show-default-value-if-field-left-empty-in-button-form/9886 "2025-10-26T09:57:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [October 26, 2025, 9:57am UTC](https://community.fibery.io/t/show-default-value-if-field-left-empty-in-button-form/9886/1 "2025-10-26T09:57:06Z")

</div>

Here is a use case, which is purely a UX (transparency of automation) need:

Two issues:

1. User needs to know what happens if the fields are left empty. Often an automation applies a default value, we need the user to see that before they hit Run.

- Either (simple) just a manual comment in the button form (‘defaultvalues when left empty are xx xx etc)
- or (which is better) _t **o-one relations get a default value setting in their field configuration 🥳 🥳 🥳 which then should be shown in the button form.** _

1. in this specific example below, numeric field gets assign ‘0’ instead of empty. This is a problem and assumption that should not be there. It leads to _ **DATA LOSS** _🥵 (the existing field values) because people think 0 means ‘not changing’ or they need to manuall remove the 0 to not overwite the existing values.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/298c4d83c390640de1d54a783014e43b94fd97bd.png)