carminez Posted August 17, 2009 Share Posted August 17, 2009 I am using JasperServer Professional 3.5.1. I'm trying to remove the repeating page headers in Excel and CSV exports by using the jasperreports.properties file, but it does not seem to work. These same settings worked correctly in JasperServer 3.1. net.sf.jasperreports.export.xls.exclude.origin.band.1=pageHeadernet.sf.jasperreports.export.xls.exclude.origin.keep.first.band.1=pageHeadernet.sf.jasperreports.export.csv.exclude.origin.band.1=pageHeadernet.sf.jasperreports.export.csv.exclude.origin.keep.first.band.1=pageHeader Similar settings for columnHeader seem to work properly, but not for pageHeader in either Excel or CSV. Any ideas? Is this a confirmed bug or am I doing something incorrect? I am using this reference: http://jasperforge.org/website/jasperreportswebsite/trunk/config.reference.html Post Edited by carminez at 08/17/2009 02:59 Link to comment Share on other sites More sharing options...
Teodor Danciu Posted August 19, 2009 Share Posted August 19, 2009 Hi, Are you sure it is the same report that runs differently in the two different versions of JS?I mean, could it be that the report has these properties overriden inside the JRXML and no longer works like it used to? Thank you,Teodor Link to comment Share on other sites More sharing options...
Teodor Danciu Posted August 19, 2009 Share Posted August 19, 2009 Hi, I have tested this on a fresh installation of JasperServer Pro 3.5.1 and seems to be working fine. So I cannot confirm this as a bug. There must be something going on in your environment. Maybe you are not modifying the right file? Thank you,Teodor Link to comment Share on other sites More sharing options...
carminez Posted August 20, 2009 Author Share Posted August 20, 2009 I wasn't modifying a file, I was actually working with a new report. But your comment got me thinking and I went and copied a report from our 3.1 server and put it on 3.5.1 and it exported with the intended behavior. That report was developed with iReport 3.0 I believe. This new report that I wasn't getting the correct exporting behavior was developed with iReport 3.5.2, so possibly there is something being added (or missing) to the jrxml in iReport 3.5.2 that caused this. Any ideas for what I should be looking for in the jrxml that could cause the overriding of the jasperreports.properties settings? Should I not be using iReport 3.5.2 for development of reports for JasperServer Pro 3.5.1 ??? Link to comment Share on other sites More sharing options...
Teodor Danciu Posted August 20, 2009 Share Posted August 20, 2009 Hi, Can we see the new JRXML you created, or at least a simplified version of it, if it contains confidential information? Thank you,Teodor Link to comment Share on other sites More sharing options...
carminez Posted August 20, 2009 Author Share Posted August 20, 2009 Attached is the jrxml Link to comment Share on other sites More sharing options...
shivareddyk Posted August 20, 2009 Share Posted August 20, 2009 Dear.......,extremely sorry to u.... i need small informstion from u(carminez and jasper admin),how can i migrate my community to jasperprofessional 3.5v(Eval version),please let me no,i need ur help........ i think u,bcz ur working with j s pro3.5v Regardsshiva Link to comment Share on other sites More sharing options...
swood Posted October 3, 2009 Share Posted October 3, 2009 Export your reports and other metadata from the community edition repository to a file. See the User Guide. Install the professional edition. Import the resources into your professional edition. ShermanJaspersoft Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now