Home
Analytics
Mapped values not exporting to XLSX file (Excel)
mbs_tim
<p>I have a BIRT report with an application I am starting to support. The issue I am seeing is that when a user exports the report to excel XLXS the report shows the integer value instead of the value it was mapped to in the report. When exported to XLS the mapped values are exported. First time working with BIRT reports, do I have to configure a different emitter? Is a different mapping required for XLXS?</p>
<p>Thanks,</p>
<p> </p>
<p>Tim</p>
<p> </p>
<p>Versions</p>
<p>Luna 4.4.2</p>
<p>BIRT framework 4.4.2</p>
Find more posts tagged with
Comments
JFreeman
<p>Are you using the out of the box XLSX emitter bundled with the 4.4.2 release?</p>
<p> </p>
<p>Can you provide a sample report that demonstrates how you are doing the mapping?</p>
mbs_tim
<p>Thanks for the respose... As far as I can tell it should be what was bundled, I been poking around but haven't fould a configuration seeting ofr the emittes.. I know the spudsoft.birt.emitters.excel_0.8.0.201307252232.jar is in my classpath. IS there an XML or properties file I should be looking at. Thanks Tim</p>
JFreeman
<p>Can you attach an example of how you are doing the mapping that is not carrying over to XLSX?</p>
mbs_tim
<p>Here you go .. Pretty Simple.. Select 1 as YN ,2 as Concur ,3 As Approved, from customer table (sample db) Created a table. Added Data, Mapped as follows.. row["YN"] Equal to 1 display value YES, row["CONCUR"] Equal to 2 display value CONCUR, row["APPROVE"] Equal to 3 display value APPROVE. Run report, data mapped to the values. Exported to XLXS values are not exported, raw data(1,2,3) is exported. Thanks for taking a look... Tim</p>
JFreeman
<p>Thank you for the example of your mapping.</p>
<p> </p>
<p>This looks to be a limitation with the spudsoft emitter. Using the spudsoft emitter for XLS or XLSX both have the same behavior of not carrying over the mapping. Where as the org.eclipse.birt.report.engine.emitter.prototype.excel (which is XLS only) does work with the mapping.</p>
<p> </p>
<p>I will see if there are any other options for XLSX but you may need to contact the creator of the spudsoft emitter.</p>
mbs_tim
<p>Thatnk yo Jeese,</p>
<p> </p>
<p>I do not see <span style="color:rgb(40,40,40);font-family:'Source Sans Pro', sans-serif;">org.eclipse.birt.report.engine.emitter.prototype.excel installed in my </span><span style="font-size:10.5pt;font-family:Arial, sans-serif;color:rgb(40,40,40);">environment. </span></p>
<p> </p>
<p><span style="font-size:10.5pt;font-family:Arial, sans-serif;color:rgb(40,40,40);">Tim</span><span style="color:rgb(40,40,40);font-family:'Source Sans Pro', sans-serif;"> </span></p>
JFreeman
<p>In the 4.4.2 release it should be located in the ./eclipse/plugins directory and labeled as: org.eclipse.birt.report.engine.emitter.prototype.excel_4.4.2.v201410272105.jar</p>
<p> </p>
<p>Within the designer, when going to run the report, you should see 3 excel options, View Reports as XLS, View Reports as XLS_Spudsoft and View Report as XLSX. The first "View Report as XLS", will be using this jar. The other two, XLS_Spudsoft and XLSX, will both use the spudsoft emitter jar.</p>
mbs_tim
<p>Yes the I have that jar. The XLS export works fine. Thanks for the help. I will see if exporting to XLS is OK with the user or put a case statement in my SQL and do the mapping there. Tim</p>
JFreeman
<p>You're welcome.</p>
<p> </p>
<p>Let us know if you have additional questions.</p>