Naming Worksheets for Excel Export from Reporting Services - by rsknowles

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 235985 Comments
Status Closed Workarounds
Type Suggestion Repros 7
Opened 11/6/2006 8:30:34 AM
Access Restriction Public


When exporting a report from Reporting Services in Excel format the worksheet names are defaulted to Sheet1, Sheet2... SheetN.
Sign in to post a comment.
Posted by Microsoft on 7/21/2010 at 7:15 PM
The following blog post explains how to use this feature in 2008 R2:

Reporting Services Team
Posted by Microsoft on 12/4/2009 at 3:20 PM

This feature was added in the SQL Server 2008 R2 release. You can download the November CTP to try it out.

Best regards,
Chris B.
Posted by Mitch McBride on 9/3/2009 at 3:08 PM
When was this fixed? I'm using SSRS 10.0.2531.0 which is the most recent release and I can't find the functionality. Is this an R2 enhancement? In future status updates to "Closed (Fixed)" please add the product revision.

Posted by Jamie Thomson on 6/23/2009 at 11:04 AM
This gets 5 out of 5 from me. I'm currently building some reports for a business user and they are reall annoyed that the sheets come out called sheet1, sheet2 etc.... rather than something meaningful.
In this case the "something meaningful" would be the member name that I currently have in the "Page" slicer for my report. Those page slicers are simply states (e.g. Texas, New Mexico, California etc..) and it would be great if those states appeared as the names of the sheets in Excel.

Really really hoping you can give us this one - it'd make for a much much more user friendly product. Small things can go a long way!

Posted by Microsoft on 1/11/2007 at 2:06 PM
Thanks for the suggestion. We are considering adding the support for this in a future release.
Posted by Microsoft on 11/9/2006 at 4:22 PM
Thanks for the suggestion. We are considering adding the support for this in a future release.