# Use "This" records fields to filter entity links

**URL:** <https://community.fibery.io/t/use-this-records-fields-to-filter-entity-links/6547>\
**Category:** Get Help\
**Created:** [August 24, 2024, 1:19am UTC](https://community.fibery.io/t/use-this-records-fields-to-filter-entity-links/6547 "2024-08-24T01:19:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChadL](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chadl/32/9873_2.png) [@ChadL](https://community.fibery.io/u/ChadL)\
**Post date:** [August 24, 2024, 1:19am UTC](https://community.fibery.io/t/use-this-records-fields-to-filter-entity-links/6547/1 "2024-08-24T01:19:57Z")

</div>

I have the following database structure that I’d like to use for documentation:

- Systems
  - Data Stores
    - Fields

  - Component Categories
    - System Components

Where the nested databases are on the many side of the one-to-many relationship. I also have a many-to-many relationship between system components and fields. I want to make it easy when documenting a system component (CRM workflow, function, document merge, etc) that I can pre-filter the fields lookup where the field is within the same system. In both Fields and System Components I have a lookup field on their parent entities’ System lookups. But it doesn’t look like relationship links within an entity can use “This” fields. I work on a systems development team in a holding company, so we deal with many systems, and field names will obviously repeat across them, which makes it almost impossible to search.

If this isn’t possible, do y’all suggest a better way of accomplishing this? Right now I configured the field and component name to be a formula of their parent system and category/data store. While this is helpful for searching, it isn’t ideal as our documentation grows.

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

---

<div class="post-metadata">

**Author:** ![Lee\_Denny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lee_denny/32/8158_2.png) [@Lee\_Denny](https://community.fibery.io/u/Lee_Denny)\
**Post date:** [August 24, 2024, 6:44am UTC](https://community.fibery.io/t/use-this-records-fields-to-filter-entity-links/6547/2 "2024-08-24T06:44:35Z")

</div>

Yes this would be so useful!

---

<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:** [August 24, 2024, 6:51am UTC](https://community.fibery.io/t/use-this-records-fields-to-filter-entity-links/6547/3 "2024-08-24T06:51:14Z")

</div>

Did you check this filter?

[https://the.fibery.io/@public/User\_Guide/Guide/Relation-Filters-and-Sorts-177/anchor=Using-dynamic-values--63cb8e1d-2c01-4760-9a72-bef50ec94838](https://the.fibery.io/@public/User_Guide/Guide/Relation-Filters-and-Sorts-177/anchor=Using-dynamic-values--63cb8e1d-2c01-4760-9a72-bef50ec94838)

---

<div class="post-metadata">

**Author:** ![ChadL](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chadl/32/9873_2.png) [@ChadL](https://community.fibery.io/u/ChadL)\
**Post date:** [August 24, 2024, 8:30pm UTC](https://community.fibery.io/t/use-this-records-fields-to-filter-entity-links/6547/5 "2024-08-24T20:30:50Z")

</div>

Looks like I was trying to add the filter in the entity search popup, but here it says it’s not possible. I just didn’t realize I could click “move above”, and the filter would work. I do prefer the expanded view though. So I guess this is my request for those filters be used on the expanded related entity search. We’d use it extensively!

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