# Form View: User frustration with form lack of parity

**URL:** <https://community.fibery.io/t/form-view-user-frustration-with-form-lack-of-parity/10414>\
**Category:** Ideas & Features\
**Tags:** form-view\
**Created:** [February 20, 2026, 2:41am UTC](https://community.fibery.io/t/form-view-user-frustration-with-form-lack-of-parity/10414 "2026-02-20T02:41:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\
**Post date:** [February 20, 2026, 2:41am UTC](https://community.fibery.io/t/form-view-user-frustration-with-form-lack-of-parity/10414/1 "2026-02-20T02:41:00Z")

</div>

I’ve mentioned this before, but…

There isn’t true parity between form views and forms inside other view types. The issues with the form view, as expressed by users:

1. Relationships and selects don’t keep their database and icon respectively.
2. Cannot have filters applied to the select fields, allowing invalid selections (like assigning tasks to the wrong team—or worse, the admin account).
3. There’s no “create and open” feature—you can only submit. Is this because forms can be shared externally?

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/d95c0f4bc63eb8f569b6c0834c0304293821fdea.png)  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/ebe46b2603600b4a75be9d34874e1c30f6463c49.png)

As for the forms inside other views/entities:

1. The default “new” behaviour is “compact” not “full”. I don’t think I’ve ever had a situation where I want the “compact” entity creation, and users really dislike how unpolished it feels.
2. All forms are visible at all times. This is information overload. Similarly named forms cause confusion.  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/054442b70fde0d93dfd29e61a75a78ce2ffde99f.png)
3. If I don’t want a form view accessible directly—to only allow it using the ‘+ New’ button—I’ve had to implement a hack workaround by sending that form to a folder effectively called “DO NOT TOUCH” to strongly deter users from touching it. I can’t move the form into a hidden space because that then removes it from user access entirely. I still want it visible but ONLY when users click ‘+ New’.

These are just my gripes about how all this is unintuitive from both the architect and the user perspectives. Hopefully it starts a discussion about usability and consistency.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [February 20, 2026, 7:56am UTC](https://community.fibery.io/t/form-view-user-frustration-with-form-lack-of-parity/10414/2 "2026-02-20T07:56:42Z")

</div>

Great feedback. Thank you 🙏

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [April 16, 2026, 2:19pm UTC](https://community.fibery.io/t/form-view-user-frustration-with-form-lack-of-parity/10414/3 "2026-04-16T14:19:03Z")

</div>

Now you can filter and sort relations, single- and multi-select fields in Forms (experimental feature)

> [@April 16, 2026 / gorilla Automatically link entities with more operators, Text color in rich text, Filter and sort relation selectors in Forms, Share with all users with a particular email domain](https://community.fibery.io/t/april-16-2026-automatically-link-entities-with-more-operators-text-color-in-rich-text-filter-and-sort-relation-selectors-in-forms-share-with-all-users-with-a-particular-email-domain/10744):
>
> A bulky release today with some quality of life improvements and… zero AI features (not sure whether it is good or bad though smiling_face_with_tear). Automatically link entities with more operators Before, you could use only = when describing Automatic Link Rule for a Relation Field. We extended the list of allowed operators. Now you also have: For Relation Fields: to-one relation is in to-many relation For Text Fields: starts with, ends with, contains For Date Fields: date field is within …