# Question re: Lackluster Form-View Functionality/Appearance

**URL:** <https://community.fibery.io/t/question-re-lackluster-form-view-functionality-appearance/5049>\
**Category:** Get Help\
**Created:** [August 31, 2023, 7:38pm UTC](https://community.fibery.io/t/question-re-lackluster-form-view-functionality-appearance/5049 "2023-08-31T19:38:09Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![DarrenLSchultz](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@DarrenLSchultz](https://community.fibery.io/u/DarrenLSchultz)\
**Post date:** [August 31, 2023, 7:38pm UTC](https://community.fibery.io/t/question-re-lackluster-form-view-functionality-appearance/5049/1 "2023-08-31T19:38:09Z")

</div>

Hello everyone. I’m trying to create a form for use in collecting responses by sharing the form via a generated sharing link.

My question is — is there any way to fix any of the following (somewhat lackluster) things?:

1. In _relation_ fields . . . the utter lack of any ability to _ **filter/sort** _ the universe of entities available for linking.

2. In _relation_ fields, with respect to the entities available for linking, the total absence of the usual _ **visual appearance** _ of such entities (e.g., the lack of _color_, _database icon/color_, _avatar_, etc.).

My many thanks in advance for any insights on this. Thank you.

---

<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:** [August 31, 2023, 8:09pm UTC](https://community.fibery.io/t/question-re-lackluster-form-view-functionality-appearance/5049/2 "2023-08-31T20:09:41Z")

</div>

1. No, but relation filters on form view is a feature in the backlog
2. If you’re filling in a field on a form, there should only be one type of entity to choose from, so not sure why you’d need to show database colour :-/  
If you mean showing information other than just the name field, then no, but again, there is a feature in the backlog to provide more details of entities in drop down lists (not just for form view but other places as well)

---

<div class="post-metadata">

**Author:** ![DarrenLSchultz](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@DarrenLSchultz](https://community.fibery.io/u/DarrenLSchultz)\
**Post date:** [September 6, 2023, 11:59pm UTC](https://community.fibery.io/t/question-re-lackluster-form-view-functionality-appearance/5049/3 "2023-09-06T23:59:26Z")

</div>

> [@Chr1sG](#):
>
> 1. No, but relation filters on form view is a feature in the backlog.

Thank you, Chris. I think this is a pretty crucial functionality, and I look forward to it (hopefully) being implemented sometime in the near future!

> [@Chr1sG](#):
>
> 1. If you’re filling in a field on a form, there should only be one type of entity to choose from, so not sure why you’d need to show database colour :-/

You’re right that there’s no _need_ to show an entity’s database color/icon in this context, just like there’s _never_ any such need to show an entity’s database color/icon. In my view, the showing of the color/icon here in this context — just like in any other context — makes everything look better and more visually appealing/categorized/cohesive/professional/cool, and therefore also more functional. I wonder: why do/should entities available for relation/linking in _form-view_ appear as antiseptic, boring, unpolished, basic, anemic, black-and-white things rather than in the color-coded, cohesive, awesome way in which they organically appear in literally every _other_ Fibery view?

---

<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:** [September 7, 2023, 5:39am UTC](https://community.fibery.io/t/question-re-lackluster-form-view-functionality-appearance/5049/4 "2023-09-07T05:39:29Z")

</div>

> [@DarrenLSchultz](#):
>
> just like there’s _never_ any such need to show an entity’s database color/icon.

Well actually, there are many places where it’s possible that entities from multiple databases can be visible at the same time (list, board, grid, timeline, calendar…) and so distinguishing them by db _is_ useful.  
My point was merely that the picker on form view is not one of these such situations.

---

<div class="post-metadata">

**Author:** ![Bronn](https://avatars.discourse-cdn.com/v4/letter/b/b5a626/32.png) [@Bronn](https://community.fibery.io/u/Bronn)\
**Post date:** [November 27, 2024, 5:31pm UTC](https://community.fibery.io/t/question-re-lackluster-form-view-functionality-appearance/5049/5 "2024-11-27T17:31:06Z")

</div>

> 1. No, but relation filters on form view is a feature in the backlog

Is there any update on this? I couldn’t see it on the current roadmap.

Currently forms are mostly useless to me because I want to add entities with relations and there’s still no filtering at all. It seems their current use case is mainly to create entities with no relations or relations with short lists that don’t require filtering.

It’s not the end of the world as we can add things in other ways, but more usable forms would be great.

(Apologies for necroing this post, I checked the rules and couldn’t see anything against it so I hope that it’s okay here.)

---

<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:** [November 27, 2024, 5:41pm UTC](https://community.fibery.io/t/question-re-lackluster-form-view-functionality-appearance/5049/6 "2024-11-27T17:41:14Z")

</div>

> [@Bronn](#):
>
> Is there any update on this? I couldn’t see it on the current roadmap

There is nothing planned I’m afraid.

---

<div class="post-metadata">

**Author:** ![Bronn](https://avatars.discourse-cdn.com/v4/letter/b/b5a626/32.png) [@Bronn](https://community.fibery.io/u/Bronn)\
**Post date:** [November 27, 2024, 5:58pm UTC](https://community.fibery.io/t/question-re-lackluster-form-view-functionality-appearance/5049/7 "2024-11-27T17:58:09Z")

</div>

Ah, that’s disappointing. Thank you for getting back to me so quickly though.

---

<div class="post-metadata">

**Author:** ![gomocoop](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/gomocoop/32/6349_2.png) [@gomocoop](https://community.fibery.io/u/gomocoop)\
**Post date:** [August 22, 2025, 7:37pm UTC](https://community.fibery.io/t/question-re-lackluster-form-view-functionality-appearance/5049/8 "2025-08-22T19:37:15Z")

</div>

Back on this thread to add my vote for this to be considered on the roadmap. =)

---

<div class="post-metadata">

**Author:** ![bear](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bear/32/12872_2.png) [@bear](https://community.fibery.io/u/bear)\
**Post date:** [October 18, 2025, 1:51pm UTC](https://community.fibery.io/t/question-re-lackluster-form-view-functionality-appearance/5049/9 "2025-10-18T13:51:04Z")

</div>

I am also here to add my vote. Would be useful to have this for my current client and the ones to come.

---

<div class="post-metadata">

**Author:** ![bear](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bear/32/12872_2.png) [@bear](https://community.fibery.io/u/bear)\
**Post date:** [October 23, 2025, 5:51pm UTC](https://community.fibery.io/t/question-re-lackluster-form-view-functionality-appearance/5049/10 "2025-10-23T17:51:14Z")

</div>

I may have a workaround for applying filters on forms for the form view. Will see if it works. Basically I want to add a table in between. For example, if you only want to add Projects with status = “active”, you make an ActiveProjects table and you create a Rule that adds an entity to ActiveProjects when you set a Project to “active” and when removes it again when you set it to “inactive”. With a bit of manual work this should work but I realize there are a few loose ends to figure out. But if I am too busy to do this then you can get it working quicker than me feel free to share it (and let me know how you made it work, you can even share an example Workspace as a Template that is what I will do when I have time).

Anyways my vote for Relational filters for forms still stands, it is very valuable to be able to filter easily.

---

<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:20pm UTC](https://community.fibery.io/t/question-re-lackluster-form-view-functionality-appearance/5049/11 "2026-04-16T14:20:45Z")

</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 …
