Re: how to influence the rowheight in excel output

Question

I tried to use dummy table with one row and column around the existing table with data. The properties were set as 'Autofit to Contents option' for both tables.
For both tables, i specified  - Table, Table Properties, Cell tab and uncheck the "Preferred Width" checkbox - and in Row tab uncheck specify height.
Still i see that in Excel output, the row height is increased since data is large enough to fit in one cell. Can someone help me understand if iam doing anything wrong here.
Thank you.

Answer 1

Hi,
Standard RTF table properties for autosizing and fixing table column/row/cell width/height should apply. At the time of RTF creation you don't necessarily have data representative of the size of the data you're going to get when you run the report. And using autosize to fix the width at design time will be impacted by the presence both your form fields and lack of data. So you probably do want autosized columns especially for Excel/HTML where output is not "pagesize" restricted.
Anyway, I digress, I thought I'd try to get BI Publisher (5.6.3) to put in an "auto" width or column-width for specific columns:
- tried using Word autosize - didn't work
- tried using xsl attributes (column-width) but BI Publisher seemed to ignore it.
Then strangely enough autosize worked in one of my test cases!
So here are the steps I used to get autosize with Excel consistently working:
If you are creating a new table:
1a. Table, Insert, Table, choose your number of columns/rows and choose the Autofit to Contents option (or the Fixed Column Width: Auto) option
Or if you want to autosize an existing table
1b. Select your table and go to Table, Table Properties, Cell tab and uncheck the "Preferred Width" checkbox - and in Row tab uncheck specify height
2. After the table you want appearing on your output insert another "dummy" autosize table (as per 1a), but with just 1 row, 1 column and make remove the border so it doesn't appear.
See if it works!
PS. would be excellent if Tim sees this, me thinks might be a gremlin in the code ;-)
Regards,
Gareth
Blog: http://garethroberts.blogspot.com/