Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Intelligence (Analytics)
Report export problem
purushdk
Hi,
i am using birt 2.3
I have some issues while export report into PDF OR EXCEL.
I have report called employee details.
1. As a report parameter i am using List box , list box contains All the field names.
example
1. empid, 2. empname, 3.sal, 4. unit.
Based on selected parameter i am displaying report. other columns using visibility property i am hiding.
example
suppose i had select two columns as empid, empname.
other sal and unit columns i am hiding.
in report its coming properly there is no issue.
when try to export report PDF OR Excel format, its not opening, its through error like, file is corrupted.
but when we select all 4 columns as list box parameter report is displaying properly and also while exporting PDF or Excel its working fine.
Please give me some solution to fix this issue.
Thanks & Regards,
k.purushothaman
Find more posts tagged with
Comments
mwilliams
Hi k.purushothaman,
I have not seen this issue before. Can you create a report with the sample database that has this issue on your machine and post it in here for me to run? What version of BIRT are you using?
purushdk
Hi,
i am using birt 2.3.1
I can't create report using sample db, i am pasting table dum.
/*
MySQL Data Transfer
Source Host: 192.168.2.201
Source Database: manavsofter1
Target Host: 192.168.2.201
Target Database: manavsofter1
Date: 10/1/2009 6:10:43 PM
*/
SET FOREIGN_KEY_CHECKS=0;
--
-- Table structure for man_demo_employee_experience
--
DROP TABLE IF EXISTS `man_demo_employee_experience`;
CREATE TABLE `man_demo_employee_experience` (
`ID` int(11) NOT NULL auto_increment,
`EMPLOYEE_ID` varchar(20) NOT NULL default '',
`COMPANY` varchar(50) NOT NULL default '',
`FROM_MM` varchar(50) NOT NULL default '',
`FROM_YYYY` varchar(50) NOT NULL default '',
`TO_MM` varchar(50) NOT NULL default '',
`TO_YYYY` varchar(50) NOT NULL default '',
`DESIGNATION` varchar(50) NOT NULL default '',
`JOB_DESC` mediumtext NOT NULL,
`SALARY` varchar(50) NOT NULL default '',
`CURRENCY` varchar(50) NOT NULL default '',
`TH_ID` int(11) NOT NULL default '0',
`STATUS` char(1) default '1',
PRIMARY KEY (`ID`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Records
--
INSERT INTO `man_demo_employee_experience` VALUES ('1', 'F1', 'IBM', 'JUN', '2000', 'JUN', '2004', 'HR', 'HR', '150000', 'INR', '3708', '1');
INSERT INTO `man_demo_employee_experience` VALUES ('2', '5504', 'soft', 'JAN', '1983', 'APR', '1988', 'bangalore', 's/w engg', '123344545', 'INR', '4468', '1');
INSERT INTO `man_demo_employee_experience` VALUES ('3', '5507', 'IBM', 'AUG', '2005', 'JUN', '2007', 'Software Developer', 'Developing', '20000', '0', '4557', '1');
INSERT INTO `man_demo_employee_experience` VALUES ('4', '576', 'MISSION SCHOOL', 'JUN', '2002', 'MAY', '2003', 'Teacher', 'Teacher', '0.36 lak', 'INR', '5350', '0');
INSERT INTO `man_demo_employee_experience` VALUES ('5', '576', 'VETA', 'JUN', '2003', 'MAY', '2005', 'Trainer', 'Training to students,', '0.48 lak', 'INR', '5351', '0');
INSERT INTO `man_demo_employee_experience` VALUES ('6', '14', 'M/S Enfield India Ltd', 'JUN', '0', 'MAR', '1980', '', '', '', 'INR', '5478', '1');
INSERT INTO `man_demo_employee_experience` VALUES ('7', '15', 'M/S Enfield India LTD', 'AUG', '0', 'JAN', '1980', '', '', '', 'INR', '5491', '1');
INSERT INTO `man_demo_employee_experience` VALUES ('8', '22', 'Simco', 'APR', '0', 'MAY', '1980', '', '', '', 'INR', '5500', '1');
INSERT INTO `man_demo_employee_experience` VALUES ('9', '32', 'IT Group', '0', '2007', '0', '0', '', '', '', 'INR', '5521', '1');
INSERT INTO `man_demo_employee_experience` VALUES ('10', '32', 'Pricol', '0', '0', '0', '0', '', '', '', 'INR', '5522', '1');
INSERT INTO `man_demo_employee_experience` VALUES ('11', '32', 'Develop India', '0', '0', '0', '0', '', '', '', 'INR', '5523', '1');
INSERT INTO `man_demo_employee_experience` VALUES ('12', '99', 'BEMEC', '0', '0', '0', '0', '', '', '', 'INR', '5565', '1');
INSERT INTO `man_demo_employee_experience` VALUES ('13', '99', 'RAM Packings', '0', '0', '0', '0', '', '', '', 'INR', '5566', '1');
INSERT INTO `man_demo_employee_experience` VALUES ('14', '164', 'Kalaimagal Polytechnic', 'AUG', '1985', 'MAY', '1987', 'Instructor', '', '0.0', 'INR', '27294', '1');
mwilliams
k.purushothaman,
I'm unable to reproduce your issue with this data in a way I can run it. If you can recreate it with flat file dataSources and attach the report, that'd be great.
IrinaD
Hi,
I have a same problem. My report has table with 12 columns. Columns 3-12 may be visible or unvisible according to specific condition. The report is displayed correctly, but export report doesn't work in case when last column is unvisible. If all columns are visible, export report is ok.
Did you find a solution?
Thanks,
Irina
mwilliams
Hi Irina,
Can you recreate this issue with the sample database at all, so I can see it?
IrinaD
Hi Michael,
The problem is not recreated with sample database.
Irina
IrinaD
Hi,
I replicated the problem. My table has 12 columns. Part of them or all may be displayed according to report parameters: start and end date.
There is a lable placed on table's footer on cell merged from 12 cells.
When I try to export report, I get error:
+ org.eclipse.birt.report.service.api.ReportServiceException: Error happened while running the report ... etc
The problem is in the merged cell. If to remove it, export report is generated.
When less than 12 columns displayed excel and other formats don't know how to handle the cell that is extended to 12 columns and generates errors.
rptdesign is attached.
BR,
Irina
mwilliams
Irina,
What version of BIRT are you using?
IrinaD
Hi,
I work with version 2.3.1.
BR,
Irina
mwilliams
Irina,
A workaround could be to create a row for each possible size of label in the footer and then drop or hide the unneeded labels based on the report parameters.
I have the Tribix XLS emitter in 2.5, so I'll have to reinstall the BIRT XLS emitter to see if it works in 2.5 as expected, but the report you posted that doesn't work in 2.3, does work in PDF in 2.5.