SSRS Report : Export to Excel - by jlenin

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<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 685238 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 8/23/2011 1:03:53 PM
Access Restriction Public



I have developed few SSRS reports in SQL Server 2008 R2 for one of our customers. I have deployed those reports to Reporting Server URL. All users are able to access and print reports. When the user wants to export to excel, it just exports as same format as it is printed on screen. It exported excel is not at all in user friendly format. It has the following problems:
1. Unwanted additional blank rows & columns.
2. Data exported fields are not fit into one cell. It scattered and merged few cells to display data of that field.
3. Exported excel data sheets cannot be used for sorting & filtering and also other excel functions.
4. Ctrl+F is also not functioning since the data in each cell has empty trail spaces.

I have suggested users to use XML & CSV exports. This is exporting just as table with unwanted header labels and not in the same order as put on the report layout. I think this is just exporting the data as table export. If they have any subtotals, subtotals are not getting exported to XML/CSV files.

User are also facing problem with Print Page Setup to print as pdfs. They cannot have option to fit the complete report to an A4 page. Page setup option which provided by SSRS report is limited.

I am really having tough time with SSRS reports. I appreciate if you can help me in sorting out all the above issues.

Sign in to post a comment.
Posted by Microsoft on 11/11/2013 at 5:41 PM
Thank you for your feedback. As you described, this is the by design behavior for this feature. Below is a blog with some best practices that should help.

If this does not help resolve your issue, please contact Microsoft Customer Service and Support.

Matt Jones
SSRS Tiger Dev
Posted by Robert Heinig II on 6/20/2012 at 4:14 AM
The Excel Exporter tries to produce a *visually* matched layout, including current drilldown state, and has done so since at least SQL 2005.

It needs emphasis - it achieves that goal admirably. The logic it employs must be complex indeed. The guys who implemented this must be fiendishly clever. No irony indended!

Regrettably, no one I know has a use for this feature. I have to explain this again and again to my users. Most of my reports are now almost useable as an Excel export by dropping any Logo, Header, Title, Parameter documentation, pagination and other output outside of the single main tablix if rendering to excel is detected. For usability as, e.g., a mail merge input, one still needs to open it and delete rows 1 and 2.

Idea: How about an option that simply prevents the renderer from mapping a textbox containing anything other than static text to a merged excel cell? If this were doable without too much overhead it would solve a lot of our gripes.

I do see one or two clean options using current stable products, but it's far too expensive: 1) Use the XML renderer and post-process using a report-specific xslt to the little documented excel 2003 xml format. XML without postprocessing is worthless as Excel input - Excel uses the xsi:schemaLocation attribute, which a) is not available after transport of the data to a different network, b) changes over time as it includes the user's session, c) randomizes the field order... or 2) Write your own renderer with insufficient documentation or sample code.

My big (meaning utopic) wishes in this context would be -
- Excel renderer becomes open source
- Control over the schema emitted by the XML renderer (would have to be able to react to the user's parameter choices)
Posted by MarcoViY on 3/28/2012 at 7:59 AM
I am getting unwanted blank rows when exporting to Excel too when working with subreports. I hope at least we can get the blank rows issue solved :)
Posted by Microsoft on 2/1/2012 at 11:30 AM
Hi there,
Thank you for filing this feedback. We have these items tracked as design change requests. It is unfortunate that we don't have the resource to implement these for the immediate upcoming release, however, we have them tracked on our backlog for future releases.
Thank you,