# 🦜 April 2, 2026 / Show Fields from relation without Lookup, AI Integration Agent

**URL:** <https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679>\
**Category:** Changelog\
**Created:** [April 2, 2026, 1:09pm UTC](https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679 "2026-04-02T13:09:40Z")\
**Posts on this page:** 1\
**Showing post:** 35

<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:** [April 10, 2026, 9:06am UTC](https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679/35 "2026-04-10T09:06:14Z")

</div>

> [@Jonathan1](#):
>
> Could you please consider adding access to related fields in a “too many” relationship on filters for a future update ?

The problem you faced does not actually require ‘access to related fields for a to-many relation’. What is currently missing is a ‘contains’ function for collections.

For example, your case would be solved if a single formula was possible as follows:

`[Step 1 Task].[Assigned To].Filter([Project Management Setting].[Tasks Notifications] contains "Start Date")`

I think what you need is this:

> [@"Contains" formula function](https://community.fibery.io/t/contains-formula-function/10178):
>
> For comparing strings, as well as comparing a collection and a single entity. Does entity x exist in collection y. Possible with the workaround “Find()” function, but a lot less clean.

---

_[View the full topic](https://community.fibery.io/t/april-2-2026-show-fields-from-relation-without-lookup-ai-integration-agent/10679)._