[Status: Backburner ⌛️] Aggregation Function (Sum and Average) in New Table View
We have been using Table view to aggregate fields related to times, quantity and costs – mostly using the Sum function – so we can see, at a glance, calculated data related to projects.
In the new Table view, the aggregation option works differently and there is no way to make certain calculations within Wrike. For example:
- You can only aggregate custom fields that are plain numbers, you cannot aggregate fields that incorporate formulas i.e. you can't sum the results of calculations from formulas.
- You can only sum at project level i.e. you used to be able to get a calculation of the sums of sub-tasks within parent tasks.
- When you turn on the aggregate function for a project with sub-projects, it gives a total without turning on the aggregated sum function for all of the subprojects within the project i.e. to see individual project sums, you have to click and aggregate every sub-project within a project individually. In the old Table view, doing this for a parent project would switch the function on for every sub-project and parent task within.
We use Wrike for much more than just task management. The reporting and financial calculations within Wrike are fairly basic as is but if the new Table view is rolled out in Lightspeed, we will not be able to do any of the finance-, resource- and volume-related calculations we need for project management.
Please incorporate the previous Aggregation functionality of Table view into the new Table view!
Hi Karen Reijneveld, what if you created an automation rule that would move an item to some other project when the status is set to “canceled”? Can that help?
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Lisa Hana Jo @...
We're running into the same limitations. Any update on this? Can we expect an accurate sum that honors filters any time soon? This is a big limitation.
Lisa, I tried creating a new formula field that equals the effort field as you seemed to suggest in a previous post, but it still does not honor the filters in place. Can you elaborate on how this work-around should be done?
Hi Caleb Scharf, I don't have an update at the moment, but I asked our Support team to look into this for you.
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Hello !
I do agree that this modification is such a mess...
Now, no way to SUM the numbers to check for example the global "to be done" in our AGILE mode.
It is also impossible to make a real SUM of expenses (budget) when it is under different levels of project tree...
This is really difficult to work in that way...
Hello Christophe DEROT, welcome to the Community! Thank you for adding your vote for this suggestion. I've passed your feedback on to our Product Team 👍
I'm specifically looking to Sum Time Spent at the task level. It will work at the project level, but not at the task, which is incredibly limiting for projects where tasks are project phases.
I hope this workaround proves helpful for your use case! If you need further assistance, please let us know. I can also raise a support ticket on your behalf if needed. Thank you!
Rohan V Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Rohan V Wrike Team member Become a Wrike expert with Wrike Discover
Chiming in on this one way late to say that this is a good feature to prioritize. We have been using custom fields to help us record the due dates and actual completion dates per step in our custom workflow, and using custom fields with formulas to calculate variance and number of days overdue. Being able to see average variance per project and per set of projects in tables and dashboards (without having to export a spreadsheet every time) seems like a natural next step to make this useful. We'd also like to see the average number of days it takes to get through the entire custom workflow, but again, we can't since this is a formula-calculated custom field. Just having this feature automatically work for certain fields makes it useless for our Wrike implementation.
Rohan V Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Rohan V Wrike Team member Become a Wrike expert with Wrike Discover
Hi Wrike Product Team, any update on Hana's bullet point #1: "You can only aggregate custom fields that are plain numbers, you cannot aggregate fields that incorporate formulas i.e. you can't sum the results of calculations from formulas."? We have a custom field with a formula, which won't sum up - which defeats the purpose of the view - see snapshot below: it's the "Test Remaining Budget" and "Test % Remaining Budget" columns that I'm seeking to be summed up...
Hi Julia, this is indeed an annoying limitation that pops up a lot. A workaround I've implemented many times before is to create a mirror custom field that auto-updates to the value of your formula field upon change. Then you use that mirrored custom field for all of your aggregations. You would either need Wrike Integrate (possibly with lots of WI tasks available) or a once-off API implementation. Feel free to get in contact if you need more help.
Lisa Is there any update on this. We just ran across this limitation.
With 176 upvotes and the functionality having been previously available (man, do I miss Old Table View every day...), is there a reason why this can't be implemented? I still need this functionality - I used it regularly and it made reporting so much simpler.
Indeed, I too miss the Old Table View exactly for that reason. Please bring this to "new" table ASAP.