# How apply a filter to the survey portal?

**URL:** <https://the.fmsoup.org/t/how-apply-a-filter-to-the-survey-portal/4782>\
**Category:** Floating Topics\
**Tags:** community\
**Created:** [April 2, 2025, 6:57am UTC](https://the.fmsoup.org/t/how-apply-a-filter-to-the-survey-portal/4782 "2025-04-02T06:57:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Saeed](https://avatars.discourse-cdn.com/v4/letter/s/e8c25b/32.png) [@Saeed](https://the.fmsoup.org/u/Saeed)\
**Post date:** [April 2, 2025, 6:57am UTC](https://the.fmsoup.org/t/how-apply-a-filter-to-the-survey-portal/4782/1 "2025-04-02T06:57:23Z")

</div>

I’ve created a new table in my database called “Survey” and established a relationship with the “visiting\_system” table using `_PK` to `_FK`.

My goal is to display the Top 5 Satisfied entries for each Department and Host Name using portals on the `visiting_system` layout. Additionally, I’ve implemented global filter fields (`g_filter`) to allow filtering by Weekly, Monthly, and Annual timeframes.

However, I’m encountering challenges getting the portals to reflect the correct filtered results based on satisfaction level and selected date range. Any guidance or recommendations would be appreciated.

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/fmsoup/original/2X/e/eb15df30044773ab0b804c28acb978d0fbb186a2.png)

---

<div class="post-metadata">

**Author:** ![planteg](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/planteg/32/627_2.png) [@planteg](https://the.fmsoup.org/u/planteg)\
**Post date:** [April 2, 2025, 10:51pm UTC](https://the.fmsoup.org/t/how-apply-a-filter-to-the-survey-portal/4782/2 "2025-04-02T22:51:04Z")

</div>

I don't know how large is the table your portal is displaying records from, but there is one thing for sure, you wish the portal will display the data in a timely fashion.

I you set a filter on the portal, then **all the rows in the table** will have to be downloaded to the client computer for the the portal to then filter. If you filter on the relation then the chore will be done on the server and only the relevant records will be pushed to the client. Without more knowledge of your system, it's hard to offer more advises, but a virtual table could be solution.

Hope that helps