# Formula fields that are filtered by the context they're viewed in

**URL:** <https://community.fibery.io/t/formula-fields-that-are-filtered-by-the-context-theyre-viewed-in/6623>\
**Category:** Ideas & Features\
**Created:** [September 10, 2024, 7:55pm UTC](https://community.fibery.io/t/formula-fields-that-are-filtered-by-the-context-theyre-viewed-in/6623 "2024-09-10T19:55:56Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\
**Post date:** [September 10, 2024, 8:57pm UTC](https://community.fibery.io/t/formula-fields-that-are-filtered-by-the-context-theyre-viewed-in/6623/5 "2024-09-10T20:57:02Z")

</div>

Aggregations by row/column in board view would likely cover many of the situations I’m thinking of.

My only issue with aggregations on table view is that they can’t be filtered. Here’s a request I made a few weeks back about it: [Allow specific databases to be excluded from column calculations](https://community.fibery.io/t/allow-specific-databases-to-be-excluded-from-column-calculations/6513)

I usually default to formula improvements being an ideal solution because the more they get improved the more flexibility and autonomy all your users have to customize their workspaces themselves without waiting/relying on specific feature requests that might never be prioritized. 🙂

---

_[View the full topic](https://community.fibery.io/t/formula-fields-that-are-filtered-by-the-context-theyre-viewed-in/6623)._