# Turn off auto-setting fields based on filters

**URL:** <https://community.fibery.io/t/turn-off-auto-setting-fields-based-on-filters/10626>\
**Category:** Ideas & Features\
**Tags:** filter\
**Created:** [March 23, 2026, 4:49pm UTC](https://community.fibery.io/t/turn-off-auto-setting-fields-based-on-filters/10626 "2026-03-23T16:49:55Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [March 23, 2026, 5:53pm UTC](https://community.fibery.io/t/turn-off-auto-setting-fields-based-on-filters/10626/4 "2026-03-23T17:53:09Z")

</div>

> [@Nathan\_Arthur](#):
>
> and that fixed the problem when new entities are created. It’s clunky, but it works.

Ooh that’s a smart way around it too!

Are they single selects or a to-relation to a database? There may one more workaround if they are a to-one relation.

If it’s a to-one. You can filter by the name of the type, and not the status entity itself:

 ![Screenshot 2026-03-23 at 17.55.24](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/71275df19d7cf4b1ff5d4dd231814f5acad1e5b3.jpeg)

Then it also won’t auto-populate.

Some potential future problems:

1. If you’re doing “is not” and selecting all the options, if you add an option later you’ll need to go in and configure all the views you did that in.
2. If you’re filtering by text name and you change the type name later, you need to change the filter in all the views you configured this.

---

_[View the full topic](https://community.fibery.io/t/turn-off-auto-setting-fields-based-on-filters/10626)._