Wich version of Jaspersoft Studio with iDempiere 7.1?

[Andreas Sumerauer]

Hi there,
I have again made the mistake and updated that Jaspersoft Studio plugin in eclipse (to version 6.14) . Now my reports are not loaded anymore.
Does anybody know the latest version of Jaspersoft Studio that can be used to compile reports for iDempiere 7.1 (latest)
Thanks so much!

[pvander...@askey.nl]

Hi,

AFAIK the latest that works is version 6.5.1.

I work with 6.14.0, but I have set it in Window/Preferences/Jaspersoft Studio/Compability to 6.5.1

Op maandag 5 oktober 2020 om 13:13:46 UTC+2 schreef reua...@gmail.com:

[Andreas Sumerauer]

Thanks for the info.

Are you using jrxml or jason files? 
I would want to use precompile jason but I have had no luck installing an older compiler. 
I was able to download the Jaspersoft report compiler but without the dependencies it won't run.

[pvander...@askey.nl]

I use jrxml.

Op maandag 5 oktober 2020 om 14:13:02 UTC+2 schreef reua...@gmail.com:

[Andreas Sumerauer]

Thanks again,
I tried and switched to jrxml but found that my subreports are not loaded.

Since I needed to get over this fast I did not bother to investigate further and installed the complete Jasperstudio 6.5.1.
Still if anybody has an Idea why my jrxml subreports don't get loaded I'd be happy to know.

Although my reports do work again I am not really happy because I am used to having the Java IDE, DBeaver and Jasperstudio integrated within a single Eclipse installation.

Does anybody know where to find the Jasperstudio 6.5.1 eclipse Plugin? It looks like it is not available anymore.

Andreas

[pvander...@askey.nl]

Hi Andreas,
I am not an expert at all, but I thought that I read somewhere that both main and sub should be made with the same version and the subs in my mains are still mentioned as .jasper.
Hope this helps.
Pieter

Op maandag 5 oktober 2020 om 22:08:35 UTC+2 schreef sume...@kanzlei-wmv.de:

[Andreas Sumerauer]

Thanks Pieter for pointing that out,
I had in fact referenced the jrxml versions of the subreports. I have now changed the references back to jasper but still had no luck in getting it going.
Andreas

[pvander...@askey.nl]

Do you have, besides the jrxml files, also some old .jasper files attached to your reports by any chance?

Op dinsdag 6 oktober 2020 om 15:44:05 UTC+2 schreef sume...@kanzlei-wmv.de:

[Martin Schönbeck]

Hi Andreas,

you know, that the subreport must be name ReportnameSubreportsomething.jrxml

Regards,

Martin

[reua...@gmail.com]

Are you really sure about that? My (compiled) subreports just work fine without following that convention.
I also have to say that this rule if it exists does not make any sense to me. 
I am using subreports primarily as building blocks that I am using with different parent reports. 

Like document footers, header and address field. I obviously would not be able to do that if the name of the parent report were part of the subreport name. 
   

[Martin Schönbeck]

Hi Andreas,

this

                // Locate subreports from local/remote filesystem
                subreports = reportDir.listFiles( new FileFilter( jasperName+"Subreport", reportDir, fileExtension));

seems to require this. I didn't test it, so I may be wrong.

I agree that the naming convention is a bit irritating. But you can of course use the same subreport for several reports if you copy it or create symlinks.

Regards,

Martin

[Diego Ruiz]

Hi Andreas,

Check the comment from Patric on this thread: https://groups.google.com/g/idempiere/c/rvfiESeb3PQ/m/Z8s33PK-AwAJ. That might be the missing piece.

You need a parameter in your main Jasper named "SUBREPORT_DIR", and the subreport Expression in your main-report must be $P{SUBREPORT_DIR}+YOUR_SUBREPORT_NAME.jasper.

Best regards,

Diego Ruiz

[Andreas Sumerauer]

Thanks Diego and Martin. This explains a lot. 
Without having looked at the code I would presume that the naming convention is there to make sure all subreports can be found by the compiler. so that the jasper files are available for the renderer. I at least never had any problems providing precompiled jasper files that did not follow that naming convention.
Anyway it is good to know how things are meant to work. I consider changing to jrxml and then I will surely have to 

[Diego Ruiz]

I'm not 100% sure about the naming convention. I think we have a generic Footer.jrxml subreport, which we use in different master reports and it works properly.

Best Regards,

Diego Ruiz

--
You received this message because you are subscribed to the Google Groups "iDempiere" group.
To unsubscribe from this group and stop receiving emails from it, send an email to idempiere+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/idempiere/75e278de-2e12-437e-ad3e-bea0dfcd6321o%40googlegroups.com.

--

Regards,

Diego Ruiz

[Leszek Bober]

Hi

In my case Jasper v 6.10 works fine at iD 5.1 and 7.1

[Chuck Boecking]

Sending for future reference:

How do you know what version iDempiere is using:

1. find /opt/idempiere-server/ -name *jasper*
2. note for 7.1: ./plugins/net.sf.jasperreports.engine_6.6.0.jar

Note you can change the compatibility per previous post:

=> Window/Preferences/Jaspersoft Studio/Compability to 6.x.x