mortias

if you do an export it updates the linked resources, meaning if you have a datasource X(1) pointing in dev to dev, and a datasource X(2) (same name) in test pointing to test when you import the report with datasource X(1) from dev to test, it updates the X(2) to X(1) ! which is not correct, it should use X(2) because it's declared but it shouldn't update it (or at least you should be able to choose it (merge/delta)

Changed Assigned User from @User_306070 to @anonymous well if it's not a bug for sure it's a feature, but it's not a question!

Changed Priority from Normal to Immediate Changed Reproducibility from N/A to Always System Message

Changed Priority from Normal to Urgent Changed Severity from Major to Trivial Changed Assigned User from - to @User_306070

Changed Severity from Minor to Trivial Changed Assigned User from - to @User_306070

I think i have found a solution to this problem, due to the fact i also had this error and solved it. So i've exported a export.zip, modified it, zipped it and i got also this error .. Solution, if you have an export folder and you zip it, you'll see an /export/ path in your zip file and that's why he doens't accept it, so you need to re-zip your zip file in the export folder .. Meaning your zip file shouldn't contain any parent folder.. you see? :) below an invalid re-zipped export.zip file to illustrate the problem cheers

Hello, I have the impression that the default settings defined in the applicationContext file are not used by the applicationContext-rest-services... do i also need to specify my exporter settings there? tx <bean id="xlsExportParameters"class="com.jaspersoft.jasperserver.api.engine.jasperreports.common.XlsExportParametersBean"> <property name="detectCellType" value="true"/> <property name="onePagePerSheet" value="true"/> <property name="removeEmptySpaceBetweenRows" value="true"/> <property name="removeEmptySpaceBetweenColumns" value="true"/> <property name="whitePageBackground" value="false"/> <property name="ignoreGraphics" value="false"/> <property name="collapseRowSpan" value="true"/> <property name="ignoreCellBorder" value="false"/> <property name="fontSizeFixEnabled" value="true"/> <property name="maximumRowsPerSheet" value="0"/> <property name="xlsFormatPatternsMap" ref="formatPatternsMap"/> </bean>[/code]

Hello, As we are moving forward with our architecture i'm trying to find a decent solution to use jasperreports with svn so we can version our reports, also to be able do move reports from dev to test and prod with the ability to change the datasources on the way? Is it even possible to install jasperreports but to keep the file structure outside the database on disk? i"ve found some solutions but nothing really ops related. tx

refr. http://community.jaspersoft.com/jasperreports-library/issues/2975-0

solution found, set the ignore pagination to false and the page size to 9999999 then all tabs will work fine with included subreports and will paginate on the line breaks included

a very simple example if i enable the pagination, it breaks via the line breaks in multiple tabs.. but in longer reports it keeps paginating.. if i disable the pagination because i'm using xls then it doesn't break the tabs anymore, seems this check is switched? <?xml version="1.0" encoding="UTF-8"?> http://jasperreports.sourceforge.net/jasperreports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jasperreports.sourceforge.net/jasperreports http://jasperreports.sourceforge.net/xsd/jasperreport.xsd" name="XlsFormulaReport" pageWidth="595" pageHeight="842" whenNoDataType="AllSectionsNoDetail" columnWidth="555" leftMargin="0" rightMargin="0" topMargin="0" bottomMargin="0" isIgnorePagination="true" uuid="fd50d991-2d4f-4d54-a851-55227b429a01"> tst tst tst

Hello, To be short, after we upgraded our jS cp 4.7 to 5.1 all our excell reports that contained multiple tabs don't work anymore everything is displayed on the same first tab.. i'm almost sure this is a bug in 5.1 (or something changed in the configuration to make it happen) i see other people reported this somewhere else (google) but didn't got any answer this is quite urgent i hope for a quick solution because it's on our production server.. tx