nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

unable to see all the columns in a report when exported to excel

krusifier

hi i have a report which has approximately 300+ columns. When i am seeing it in preview i am able to see all the columns but when i export it to excel i am not able to view all the columns in this report. On the other hand when i get somewhat less columns in excel it works fine.

Find more posts tagged with

Comments

Jenkinsj5

Duplicate question,

Good answer here

http://www.birt-exchange.org/org/forum/index.php/topic/28967-unable-to-see-all-the-columns-in-a-report-when-exported-to-excel/

wirzbicki

Simple answer is the the excel emitter is ms-2003 that has a 255 column limit and the rest of the columns are dropped or not shown.

Use a 2007 excel emitter that has 1024 columns (I believe) if you need it...

Also if you have column merging going on in your report which can occur in crosstabs you to can eliminate the merging (thus returning some more columns back to the report) by making sure that each section (control break) is balance with the same number of columns so that column merging will not occur.

Mike W.

Yaytay

<blockquote class='ipsBlockquote' data-author="'wirzbicki'" data-cid="114908" data-time="1362755461" data-date="08 March 2013 - 08:11 AM">
Also if you have column merging going on in your report which can occur in crosstabs you to can eliminate the merging (thus returning some more columns back to the report) by making sure that each section (control break) is balance with the same number of columns so that column merging will not occur. </blockquote>
 
In a similar vein, some Excel emitters introduce superfluous oulmus for formatting reasons - if you have a label in a cell and both the label and the cell specify border formats the only way to provide the two borders in Excel is by adding tiny exta columns/rows. 
The Tribix emitter is the worst for this, it provides very precise layouts by introducing LOTs of superfluous rows/columns, but the built in emitter (and presumably the Native emitter which is built from the same code base) also does it to some extent. 
The SpudSoft emitter doesn't do it at all, which means you simply can't have a border on the cell AND and the contents with that emitter (but you will get one cell in the output for each cell in the input). 
 
Jim

krusifier

how can we use(install) spudsoft BIRT excel emitter in ibm websphere.
Please provide a set of instructions.

Yaytay

<blockquote class='ipsBlockquote' data-author="'krusifier'" data-cid="114962" data-time="1362993651" data-date="11 March 2013 - 02:20 AM">
how can we use(install) spudsoft BIRT excel emitter in ibm websphere. 
Please provide a set of instructions. </blockquote>
The simple answer is that I don't have a clue, I don't use websphere and you haven't said anything about how you have BIRT deployed in it. 
Before I could even begin to say anything useful I'd need to know what version of BIRT you are using, whether you are using it as an OSGi platform or as a POJO platform. 
 
Jim

krusifier

I am already using BIRT in websphere. In websphere i've created a separate project for birt. My birt version is 3.7.2 and i am using it as a POJO platform