Showing posts with label excel. Show all posts
Showing posts with label excel. Show all posts

Monday, March 26, 2012

Max # of columns in Excel Export

I am exporting a report which consists of one simple table. The data is
simply exported to excel.
I am noticing that if I add more than 65 columns to the report (i.e. 66 or
more) then, after exporting to excel, there is a problem re-sizing the
columns in excel. For some reason the data automatically gets a line wrap
character within the cell, and double-clicking the column to resize it
effectively does nothing.
Specifically, my data in column #34 looks like:
"Here is a really really really long sentence." <- there are no carriage
returns
If you double click on the cell the data goes into, in Excel, it ends up
displaying like:
"Here is a" <--
"really really" <-- all of this is in ONE cell in the spreadsheet.
"really long" <--
"sentence" <--
How can I overcome this? Or how can I change how the expansion is handled
in Excel?
Thanks!
DavidMore specifically, if I have more than 65 columns, then the "wrap text"
checkbox is checked (and applied) for all columns/rows in Excel. If I have
65 or less, it is not.
"david boardman" wrote:
> I am exporting a report which consists of one simple table. The data is
> simply exported to excel.
> I am noticing that if I add more than 65 columns to the report (i.e. 66 or
> more) then, after exporting to excel, there is a problem re-sizing the
> columns in excel. For some reason the data automatically gets a line wrap
> character within the cell, and double-clicking the column to resize it
> effectively does nothing.
> Specifically, my data in column #34 looks like:
> "Here is a really really really long sentence." <- there are no carriage
> returns
> If you double click on the cell the data goes into, in Excel, it ends up
> displaying like:
> "Here is a" <--
> "really really" <-- all of this is in ONE cell in the spreadsheet.
> "really long" <--
> "sentence" <--
> How can I overcome this? Or how can I change how the expansion is handled
> in Excel?
> Thanks!
> David|||> Or how can I change how the expansion is handled in Excel?
David,
In Excel, hit Ctrl-A to select the entire active range then go to
Format/Cells.../Alignment and uncheck 'Wrap text'.
HTH,
Chris|||Hi Chris - thanks for the reply. I'm curious as to why this happens with
more than 65 columns of data. It's just an annoying extra little step that
the receivers of this report have to do. If at all possible I'd like to
eliminate it as, like I said, this doesn't happen with less columns of data.
Strange...
Dave
"Chris" wrote:
> > Or how can I change how the expansion is handled in Excel?
> David,
> In Excel, hit Ctrl-A to select the entire active range then go to
> Format/Cells.../Alignment and uncheck 'Wrap text'.
> HTH,
> Chris|||Yeah, I would agree that it is annoying and odd that it only happens when
there are more than 65 columns in the output. Sorry I can't be of more help.
Chris

Friday, March 23, 2012

Matrix w/ Subtotals Export to Excel rrRenderingError

Is it possible to export a matrix report that has subtotals on multiple
columns to Excel? With just the innermost group subtotaled, I don't get an
exception, but when I add subtotals for outer groups it will not export.
I've seen this question posted elsewhere, but no answer to it. Thanks!Magpie,
I have same problem. Do you have any idea of solution?
Regards,
Loretta
"Magpie" wrote:
> Is it possible to export a matrix report that has subtotals on multiple
> columns to Excel? With just the innermost group subtotaled, I don't get an
> exception, but when I add subtotals for outer groups it will not export.
> I've seen this question posted elsewhere, but no answer to it. Thanks!

Wednesday, March 21, 2012

Matrix Report Exporting

I have a Matrix report in RS and I am trying to export it to Excel. The data in the report is formatted as currency. The data does transfer fine, but the currency values are stored as strings. This will not allow me to perform calculations. I have not had this problem with table reports, only the matrix. Is there any solution that be performed on the server side?

It shouldn't matter if the textbox is part of a matrix or a table. What matters is the definition of your text box: the expression you use to calculate its value, the data base field type you bound the textbox to.

Thank you,

Nico

|||The data type in the database is SQL money, and the field type in SQL RS is currency, but it exports into Excel, not as string as I originally thought, but as a custom data type that will not easily convert into a numeric data type.|||

Try this: in the matrix cell textbox, instead of just using the field value (=Sum(Fields!A.Value)), convert it into a double: =Sum(CDbl(Fields!A.Value)).

-- Robert

Monday, March 19, 2012

Matrix Report Exporting

I have a Matrix report in RS and I am trying to export it to Excel. The data in the report is formatted as currency. The data does transfer fine, but the currency values are stored as strings. This will not allow me to perform calculations. I have not had this problem with table reports, only the matrix. Is there any solution that be performed on the server side?

It shouldn't matter if the textbox is part of a matrix or a table. What matters is the definition of your text box: the expression you use to calculate its value, the data base field type you bound the textbox to.

Thank you,

Nico

|||The data type in the database is SQL money, and the field type in SQL RS is currency, but it exports into Excel, not as string as I originally thought, but as a custom data type that will not easily convert into a numeric data type.|||

Try this: in the matrix cell textbox, instead of just using the field value (=Sum(Fields!A.Value)), convert it into a double: =Sum(CDbl(Fields!A.Value)).

-- Robert

Matrix report export to Excel

I created a report based on matrix.
I set the can grow property of all fields to false.
In the report the fields are behaving as expected - the size is fixed.
When I'm exporting to excel the fields are growing according to the text size.
(I have other report based on table and the can grow property controls the
fields alos when exporting to excel).
How can I control the can grow?
Thak'sHello,
It seems that you're running into a limitation in Excel. When there are
merged cells in a row, Excel cannot apply it's equivalent of CanGrow on the
row. You're likely running into merged cells due to the layout of your
report. If items in the report don't line up with each other vertically,
SRS are forced to span items across multiple cells in order to preserve
your layout.
I have forwarded your feedback to the product team. In the meantime, I also
encourage you submit via the link below
http://lab.msdn.microsoft.com/productfeedback/default.aspx
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================Please note that the newsgroups are staffed weekdays with a goal to provide
ONE BUSINESS DAY RESPONSE to all posts.
If this response time does not meet your needs, please contact CSS for more
immediate assistance:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

Monday, March 12, 2012

Matrix export to Excel format difficulty

I made a matrix report with drilldown.

My users like to export it to excel and work with it there.

The + signs don't lie up correctly when it is exported- you have to click the '+' one row up from what you really want to expand it.

Any tips on getting the right data lined up with the right '+' on export? Thanks

How are you exporting it to excel? When I use the standard export method in Report Server, it works fine.|||The user chooses 'excel' format and then clicks export.|||

Try changing your subtotal rows Position property to "Before" instead of "After". You can get to this property by clicking on the green triangle in the corner of the subtotal row, it's in the Layout category.

|||Make sure the toogle item property is set properly.