Group by Expand/Collapse not working when default is collapsed in SharePoint 2010


All replies

  • Hi,

    There was a known post SP2010 SP1 bug with regard to expanding/collapsing grouped elements in a list view. The bug was fixed in august 2011 cumulative updates. Installing the lastest CU (If you did not yet) may solve your problem.

    - SP 2010 August 2011 CU

    - SP 2010 December 2011 CU : The updates are cumulative which mean that December CU include those of August.


    Hope this helps,


    Djamel Chagour
    • Marked as answer by Seven M Friday, December 23, 2011 7:58 AM
    Friday, December 16, 2011 2:25 AM
  • We have not applied the SP1 yet on our production and Staging servers. We applied that on our dev boxes only, which broke our sites because of the different database version number. We applied a CU for May that was released for a short time to fix one of the errors that was caused by the previous CU. After that we applied SP1 at the end of last month in Nov. After that we started getting an error when we run Configuration wizard that the database version number was different than expected. For this we have a ticket open with Microsoft and they said they know regenerated this issue on their side and the fix would be to run some script to change the database version numbers which they want us to wait until they confirm that with their database team.

    So my concern is, if we apply this August or December CU, would it break some thing or is there any solution like some javascript that we can add to the masterpage to fix this issue as described in this forum.

    Ricky Singh
    Friday, December 16, 2011 5:57 PM
  • Hi,

    I do not think there is any harm to install the CU. However, since you have a ticket open with Microsoft, I would suggest to wait for their recommandations.


    Djamel Chagour
    Saturday, December 17, 2011 6:18 AM
  • Hi,

    We have installed Feb 2013 CU and still faces the issue?

    Any thoughts on this?


    Tuesday, October 01, 2013 11:43 AM
  • Don't mean to pile on -

    but I'm running the SP2 + August updates and see this issue.   :)

    Steve Hahn

    Thursday, October 31, 2013 4:25 PM
  • I also have this issue running SP2 + August CU.

    Tony Chappell

    Thursday, December 26, 2013 5:05 PM
  • Same for me
    Wednesday, February 05, 2014 4:19 PM