# 🧐 Your opinion needed. Automations in Fibery (limitations and opportunities)

**URL:** <https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819>\
**Category:** News & Announcements\
**Created:** [October 15, 2025, 2:27pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819 "2025-10-15T14:27:17Z")\
**Posts on this page:** 1\
**Showing post:** 58

<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 28, 2025, 2:00pm UTC](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819/58 "2025-10-28T14:00:29Z")

</div>

I realise now that I misunderstood this line

> [@Eva\_Folch](#):
>
> When linking entities, it would be great to:
> 
> - Filter lookup options dynamically, ex… by **Client Name** from the current entity.

as meaning that you wanted to apply filtering to the dropdown box of options that appears _when linking items_, but I guess now it was about ‘creating a lookup collection field with filtering’.

> [@Eva\_Folch](#):
>
> Is this not the same as lookup? Like you say, with a formula, I can also not order the fields, and sorting descending by date is also not possible, right?

No, you’re right, formulas (and lookups) do not behave like ‘normal’ relation views, so if that’s essential, then your options are somewhat limited.  
But we do have that in our backlog to address:

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

Alternatively, your issue would possibly be solved by this:

> [@Automatic linking - increase possibilities beyond "equals"](https://community.fibery.io/t/automatic-linking-increase-possibilities-beyond-equals/9895):
>
> Is there a specific reason we cannot have auto-link conditions other than “=”? For my use case I would need larger or smaller than comparisons with date fields and regex / “contains” capabilities: If cost center (booking) = cost center (budget category line) Booking date (booking) \>= period start (budget category line) Booking date (booking) \<= period end (budget category line) Cost element (booking, string) [is within] Concat cost elements (budget category line) Use case simplif…

---

_[View the full topic](https://community.fibery.io/t/your-opinion-needed-automations-in-fibery-limitations-and-opportunities/9819)._