Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I have several list webparts (7-8) that all have documents that are "grouped by" a single field. The problem I'm having is that the expand button will sit at "Loading" and won't load! Some load quickly, others don't load at all. Whats the deal?

enter image description here

share|improve this question
    
It is probably some ajax not loading correctly. I would suggest starting with Fiddler (fiddler2.com/fiddler2) to help identify what might not be loading correctly between your browser and the server. –  John Chapman May 9 '12 at 16:01
    
I couldn't find where the ajax wasn't loaded correctly. Trouble is in Firefox, most of them load fine. In IE, its having problems. –  Mike May 10 '12 at 14:48
add comment

2 Answers

If "Fiscal Year" is a calculated field, change the 'data type returned' of the calculated field from "Date and Time" to "Single Line of Text". The problem in this situation is that it is requesting data for a Date object but only providing the year, which naturally does not match a fully-formed DateTime. Changing it to text makes it query the data for an exact match which should produce the results you are looking for.

share|improve this answer
    
The Fiscal Year datatype is all Single Line of Text. –  Mike May 9 '12 at 18:50
    
If that is the case, you might want to check your patch level. One of the Cumulative Updates between June 2011 and Feb 2012 resolved this on one of the lists where we saw this –  Dave Wise May 9 '12 at 19:07
    
Our Patch Level is CU Oct 2011, so that might explain something, but which one is the one I need? –  Mike May 10 '12 at 14:40
    
The Official Microsoft answer is to only apply the CU that contains fixes to issues that you are seeing. The real-world answer is to apply the most recent CU so that it can correct issues that may be present but have not yet been reported to your internal help desk yet. The most recent is the April 2012 Cumulative Update - technet.microsoft.com/en-us/sharepoint/ff800847 –  Dave Wise May 10 '12 at 15:04
add comment
up vote 0 down vote accepted

This was solved by deleting and readding the webparts. The problematic webparts were due to a post migration of ListWebPart type that was stuck in an old version. Deleting that old version and readding the new version of the webpart made it load correctly.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.