# Create Form: Add Filtering for dropdowns

**URL:** <https://community.fibery.io/t/create-form-add-filtering-for-dropdowns/9740>\
**Category:** Ideas & Features\
**Created:** [October 6, 2025, 1:43pm UTC](https://community.fibery.io/t/create-form-add-filtering-for-dropdowns/9740 "2025-10-06T13:43:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\
**Post date:** [October 6, 2025, 1:43pm UTC](https://community.fibery.io/t/create-form-add-filtering-for-dropdowns/9740/1 "2025-10-06T13:43:15Z")

</div>

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

In my current case I want to create a task and link it to a desired result (in the dropdown field). But I don’t want to show the desired results that were already achieved.

---

<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:** [October 6, 2025, 1:44pm UTC](https://community.fibery.io/t/create-form-add-filtering-for-dropdowns/9740/2 "2025-10-06T13:44:54Z")

</div>

Are you talking about being able to create entities of a related type, when submitting a form for a given type?

---

<div class="post-metadata">

**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\
**Post date:** [October 6, 2025, 1:51pm UTC](https://community.fibery.io/t/create-form-add-filtering-for-dropdowns/9740/3 "2025-10-06T13:51:53Z")

</div>

Ermm.. I didn’t think of this that way.

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

Here’s an example of a workaround I’m building to at least get an idea about the sprint date range the desired results belong to. And still it’s just a mess cause the list in the dropdown isn’t ordered by date. But I’d love to hide the irrelevant data all together without the need for such tricks.

But I think the dependent fields functionality could help here too.

---

<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:** [October 6, 2025, 2:10pm UTC](https://community.fibery.io/t/create-form-add-filtering-for-dropdowns/9740/4 "2025-10-06T14:10:41Z")

</div>

OK, gotcha.

Seems related to this topic:

> [@Question re: Lackluster Form-View Functionality/Appearance](https://community.fibery.io/t/question-re-lackluster-form-view-functionality-appearance/5049):
>
> 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?: In relation fields . . . the utter lack of any ability to filter/sort the universe of entities available for linking. 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…

---

<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:** [October 31, 2025, 9:58am UTC](https://community.fibery.io/t/create-form-add-filtering-for-dropdowns/9740/5 "2025-10-31T09:58:58Z")

</div>

Voted. The lack of this really pushes to use improper data structures. Removing a project from the database because it is complete is not great practice, but is needed in this scenario due to the lack of filtering in Form View.
