'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix SharePoint Issue Tracker View Displaying NaN for Grouped Counts
Question details
The user is experiencing a display issue in a SharePoint Issue Tracker list where grouped choice columns show 'NaN' instead of correct item counts.
- Product
- Microsoft SharePoint
- Device & OS
- not provided
- Scenario
- Filtering an Issue Tracker view by the '[Me]' variable and grouping it by a Status Choice column.
- Observed behavior
- The grouped section headers display '(NaN)' instead of the numerical count of items, despite similar configurations working correctly in other lists.
Ensure you have your exact list configuration, view settings, and Choice column details documented, as this issue often requires investigating specific view parameters to find a resolution.
Document and Report the Issue to SharePoint Support
Since this is often a specific tenant or configuration bug in SharePoint, providing detailed reproduction steps to Microsoft support is the most effective resolution path.
Display bugs like '(NaN)' in grouped views are frequently caused by backend processing errors when combining specific filters and grouping variables. Reporting this to support ensures your tenant can be investigated directly.
Navigate to the affected SharePoint Issue Tracker list and capture a screenshot or screen recording of the view displaying the (NaN) error.
Write down your exact View settings, specifically noting the filter applied (e.g., using the '[Me]' variable) and the 'Group By' column configuration.
Open a new support thread in the Microsoft Tech Community or submit a ticket through your Microsoft 365 Admin Center.
Share your screenshots, screen recordings, and list configuration details via private message with the support agent to ensure sensitive company data is protected.
Recreate the Grouped View
Sometimes a corrupted view can cause grouping display errors. Creating a completely fresh view may force SharePoint to recalculate and resolve the NaN output.
Looking for a smoother document management experience? Try WPS Office.
While SharePoint and Microsoft 365 handle cloud list tracking, WPS Office provides a lightweight, highly compatible alternative for creating, editing, and managing your standard Office documents without the complex errors.
- 1. Download the Installer: Visit the official WPS Office website to download the free installer for your operating system.
- 2. Install the Software: Run the downloaded installation file and follow the quick on-screen prompts to set up the software.
- 3. Open Your Files: Launch WPS Office and instantly start opening and editing your existing Microsoft Office files with full format compatibility.
Frequently Asked Questions
What does NaN mean in a SharePoint list view?
NaN stands for 'Not a Number'. In SharePoint, this usually occurs when an internal script or calculation fails to evaluate the item count for a grouped category, often due to a corrupted view or a bug in how complex filters interact with choice columns.
Why does the NaN error only appear in one specific SharePoint list?
List configurations, column indexing, and specific combinations of filters (like using the [Me] variable) can trigger localized bugs. A similar view in another list might not hit the same processing error due to different data types, item counts, or internal indexing statuses.
Can I fix the SharePoint NaN error by changing the column type?
Sometimes. If the issue is tied to a specific Choice column, temporarily changing it to a standard text column or modifying the choice values might force SharePoint to re-index the data and resolve the display error. However, this is a workaround and should be tested carefully.
Is it safe to share my SharePoint list screenshots on public forums?
No. You should always obscure sensitive company data, user names, and internal URLs before posting publicly. When working with Microsoft Support, provide unedited screenshots only through secure private messaging as requested by the support agent.
