|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, March 31, 2011 1:04 PM
Points: 6,
Visits: 18
|
|
I'm pretty sure SSRS doesn't do this on its own, but I was wondering if someone could help me find a third party product that could accomplish what I need from SSRS.
Specifically, I need SSRS to preserve settings when I export a report to excel for such things as excel page headers and footers, print range, column width, etc.
How can I accomplish this with SSRS, or what third party API will accomplish this?
Thanks!
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, March 31, 2011 1:04 PM
Points: 6,
Visits: 18
|
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, March 31, 2011 1:04 PM
Points: 6,
Visits: 18
|
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Sunday, February 10, 2013 11:44 AM
Points: 170,
Visits: 442
|
|
SSRS absolutely sucks when it comes to clean exports to Excel. It loves to put in hidden columns and all kinds of other trash that makes the export useless to an analyst who intends to do further work with it. It's okay for just viewing the data but if you were only doing that, why would you bother exported to Excel? It's so bad, that for our analysts I am recommending we move their reports out of SSRS and make them natively in Excel and pull in the data through ODBC directly.
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: 2 days ago @ 6:20 AM
Points: 376,
Visits: 885
|
|
The biggest issue I've seen with reports is the merging of cells. This usually happens if I have multiple tablixes on the same page that would export to being in the same tab in a spread sheet. The only way I've found to get around that is to have each tablix on its own tab, that is, page break between tablixes.
Another trick to remove "hidden" or extra rows is to be sure to line up multiple items right next to each other, in other words use the tools to have tablix2 begin immediately below tablix 1 by editing Location values.
If your users are most interested in doing pivot tables of the data exported to excel, I recommend making sure the raw data formats correctly in CSV format and then encouraging users to export to CSV output files where they can take the raw data and mush it up to their heart's content.
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Today @ 7:34 AM
Points: 427,
Visits: 92
|
|
I have also found that if you're having problems with headers (text boxes above the tablix(s)), you can just add rows above the tablix header row. Then you can merge and center as you wish, only affecting the row you specify. Also, this will not create ghost columns (blank columns between columns of data).
If this does not work for you, SSIS is going to be your best choice.
|
|
|
|