Jasper subreports with tJasperReportExec component.

[Anonymous]

Hello, 

I am using tJasperReportExec component to create PDF reports. I have two subreports within my main report which are getting referenced from a different folder location. When I run the report within JasperSoft Studio, it works fine by taking the path to subreports passed as parameters. But when I use the same set of parameters with tJasperReportExec component, it is getting ignored and throws an error saying unable to locate the .jrxml file within the same folder (where the main reports resides) instead of looking for the file in the location passed as parameter. Although the parameter variables are getting recognized, it seems the component is still looking for the subreport within the same folder as main report and not using the parameter supplied. Attached is a similar project structure to what I have where Rpt1.jrxml (main report) is making use of Rpt3.jrxml and Rpt4.jrxml as subreports.

Is this some configuration I am missing or does this component require all the subreports to be within the folder where the main report is located?

Thanks

[Anonymous]

Hello,

tJasperReportExec is a custom component written by talend community user Jan Lolling and shared on talend exchange portal.

We don't have the source code of these components. It is the ownership of the person who built it. Feel free to contact the author.

Best regards

Sabrina

[Anonymous]

Ok, thank you.

[Anonymous · Accepted solution]

The problem is the component tries to compile the reports (main report and sub reports) and therefore it needs to know where the reports are located before the actual fill and export steps starts (and when the parameters are read).

I agree with you, it should be possible. I will add an option to prevent the compile check and accept the dynamic report location by the parameter.

At the moment, you have no chance, the path must be known at design time and not at runtime.

[Anonymous]

Thank you Jan.

[jhammer98]

Has this new functionality (an option to prevent the compile check) been added yet?

I'm having the same issue with a subreport on version 5.1 with a release date of 20190328.

If it has been added, how is the option to be set?

Thanks!!!

[Anonymous]

Yes, this option is available in version 5.1