Calculate lookups on the front end (based on filters)

[helloitse]

I think this feature request is tied to the general concept of having calculations function as a part of views not as a formula field at all.
The current solution would be to create many formula fields that calculate various conditions to match a fixed set of filters. For example I have a formula that calculates the number of active sub articles in my Company manual and I display it on list views:

We’re really looking to recreate the common function in competitor tools of aggregating data about the entities in view (Sum, Avg, Count).
There’ve been several requests through the years that relate

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

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 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 …

Kanban view columns & formulas

Hey guys, Not sure if doable or not but would it be possible to allow defining custom formulas allowing to compute specific indicator based on Kanban columns content? Computed value could be located under the column title (close to the count information when displayed). [image] Cheers.

Which is also linked to Kanban board details - WIP Limits

Fibery makes us choose between views which allow us to edit and interact with the entities, and reports which aggregate information about the entities and their properties. This is a hard transition when coming from other tools which do not offer powerful reports and so have lightweight aggregations inside the views. I think there are clearly many cases for why in-view calculations should be functions of the view and not a part of the data model.