Column totals missing in modern list views
Column totals missing in modern list views.
This is an often used function, and the workaround to set the list back to classic will only be a temporary solution.
As of March 2019 this feature is available to all users of the list/library webparts on modern publishing pages, and to 50% of First Release users in the full page lists/library app. We are continuing to roll this out to all users, but it’s part of a collection of other features, and we have paused rollout a few times to address requests and changes in those other features.
Note this feature is available only in SharePoint Online
I agree with the statement that the "Modern SharePoint List" experience has been extremely frustrating with constant unnecessary changes that break or abandon such basic functionality that we've gotten used to.
When will this be available to all users in SharePoint Online? Thank you.
Veronique Palmer commented
And then you put it at the bottom of the items so we have to scroll to find it. Put it at the top, where is used to be in classic SharePoint so we can see at an instant. Why do you keep "Fixing" things that were not broken? SO frustrated with modern SharePoint!
When will this feature be available to all users?
Matthew Satterwhite commented
Here is a workaround that I came up with if your views are simple based on the value of one column:
Go into the view and click on Group By at the bottom
Set the "First group by the column" to the column that your view is on
Click Expanded in the "By default, show groupings" field
You will then see in parentheses the count of the grouping in the view
L White VA commented
Some days I have it and some days I don't. Please advise when this feature will move from peek-a-boo status to completely functional.
Josh Eliason commented
This is a feature that we actually used to have in the Modern List Experience, but it is no longer showing up. We are not a part of the First Release group - is this expected that the feature would disappear?
Alessio Bellotti commented
still no news?
Hannah Dexter commented
Looking forward to this being fixed in early 2019!
@Sharepoint Experiences Team - can you provide a reason why this was not included? A harder ETA for launch?
Well over two years... and this basic functionality that was already part of sharepoint is still missing...
Yes, getting back what we've lost! :) Thanks for bringing this useful tool back and making the modern view as powerful as the classic one, so we can finally kiss it good bye.
I don't think this Uservoice is being actively managed. If you search for ideas for "Total" in views, you'll find a dozen of suggestions with few votes each.
If the uservoice would be managed correctly, where MS would have merged all these similar ideas together the votes would be DRASTICALLY higher so they know the real pain associated with removing features that existed for 15 years!
And when they give back a basic functionality we had for 15 years, it will be done with great (fake) fanfare...
Wait a minute? Considering building this functionality?? It's ALREADY in the system, been working since Sharepoint 2003 but now suddenly produces no results in the modern view. Please add this back ASAP, my teams are not happy with the new modern views and the fact that an ID or Title column cannot be made smaller is also a problem. Modern views are great in many ways, but went backward in functionality as well. Can't wait to gain back what we already had.
Mark Small commented
What's confusing is that the "Totals" option is still available in the View Settings screen, it just doesn't show in the actual view. I was helping a new associate the other day with creating views, and the Totals option was something they really needed. So we have to switch back to Classic experience to get that. Not cool.
You should be doing more than just "considering building this functionality". It already existed in previous versions of SharePoint. And there's been no update on this request since April 2017?
I concur with all that have asked why we should have to beg for previous functionality to be reinstated, just because someone at Microsoft decides it's no longer important or needed. I'm still hurting from the deprecation of Access Web Apps, which was also pulled from service without a functional replacement.
I'm all for change and typically embrace it, but not when it means taking backward steps in an attempt to move forward.
Many are desperate for this feature - please bump up the priority list. Thanks!
We need this please
Bruce Hankins commented
Why do we constantly have to request functions we previously had? And then act like we've been given this brand new function when it has returned?