terco

Hello, is it possible to configure a report in JasperReports Server (4.0 or 4.1) the way that the users only can run it as a scheduled job? Thanks + Regards, Terco

Hello, I was surprised to find this under "[JasperReports Server] Feature Requests" and from 2008! jasperforge.org/plugins/mantis/view.php ( http://jasperforge.org/plugins/mantis/view.php?id=1312 ) Is this getting any attention or there is a reason why is not there? Maybe is it possible to configure it, even with some restrictions? Many thanks for any information, we need this in our project which is using JasperReports Server (4.0) terco Post Edited by terco at 10/21/2011 08:56

... and if you would like to also take them out from the viewer, do the same under /jasperserver/WEB-INF/flows/viewReportBeans.xml

Is it planned to resolve this limitation in a future version? Thanks

Hello Daniel, I opened a Bug for this http://jasperforge.org/projects/jasperserver/tracker/view.php?id=5459 + you can vote for it. Regards, Terco Post Edited by terco at 09/26/2011 15:28

ok, found it out: modify /jasperserver/WEB-INF/flows/reportJobBeans.xml <util:list id="allOutputFormats"> <!-- comment/uncomment any of the beans below if you want related exporters to be excluded/included in the scheduler's output formats list -->

Hello, I am looking for a way to limit the "Output Format" list when the "Schedule..." or "Run in Background" option is used for a Report in JasperReports Server (JRS). I can see following options (JRS 4.0): Output Format PDF HTML Excel CSV DOCX RTF ODT ODS XLSX and would like to hide some of them. Is that possible through a configuration file? Or other way? Thanks!

Steps To Reproduce - Create a report with cascaded input controls. - Implement the JasperReport Server Liferay Portlet (JasperReportsServer-portlet-4.0.0.war) in a Liferay application. - Call the report from the integrated JasperReport Server Portlet - Input controls which are not cascaded show all values. - Cascaded input controls are empty.

Any idea anyone. Issue logged Votes welcome jasperforge.org/projects/jasperserver/tracker/view.php Post Edited by terco at 09/22/2011 14:28

Hello, what ramnik wrote is true. Something important to take into consideration though: "When defining these parameters in a report, don’t use a defaultValueExpression element. Due to a limitation in JasperServer, these parameters are null when a defaultValueExpression is provided." And that could be difficult to see if you are not working directly into the JRXML file: once you have defined a default expression and deleted it (let that field empty in iReport), the entry <defaultValueExpression><![CDATA[]]></defaultValueExpression> within that Parameter (LoggedInUserRoles) stays in the JRXML file forever (causing LoggedInUserRoles to be null !) unless you deleted it manually!

Hello, I was able to integrate JasperReport Server (4.0) to a Liferay (5.2.3) Portal running on JBoss (4.2), but not every Input Control is showing containt as when running on the JRS, all cascading Input Controls are empty. Is this a known bug in the JasperReports Server Liferay Portlet or something I should configure differently? Thanks. Post Edited by terco at 09/19/2011 07:50

Hello, Wenn displaying a report in JasperReports Server (JRS) 4.0, one has the possibility to export the report to many formats: PDF, Excel, CSV, etc. Same formats for scheduling a report. I am now looking for XML, which I couldn't find in the JRS. In iReport (4.0) I have the possibility to set the viewer to XML: Preview / XML Preview As result I get a jrpxml file which contains the report result. Is there a (standard) way to configure something similar in JRS ? Thanks Post Edited by terco at 06/22/2011 06:40

Hello, I am trying to use the Profile Attributes within the main query of a report. The idea is to bring that information to the where clause of the query. There are Parameter available which provide this data: http://jasperforge.org/plugins/mwiki/index.php/Jasperserver/Cascading_input_controls LoggedInUserAttributes, LoggedInUserAttributeNames, LoggedInUserAttributeValues and LoggedInUserAttribute_<attribute name> So far I was able to use LoggedInUserAttribute_<attribute name> in a query, like this: select * from table1 t1 where t1.col1 in ($P!{LoggedInUserAttribute_MyAttr1}) For that, I have to save the attributes this way: [MyAttr1:'Value1a','Value1b'] with the single quotes. The problem with this solution, besides that's not elegant, is that if a user doesn't have that attribute set, it comes to a Java exception. If I use LoggedInUserAttributeValues with $X (taking out the single quotes): select * from table1 t1 where $X{IN, t1.col1, LoggedInUserAttributeValues} then all values from all attributes are inserted (not only MyAttr1 values but also MyAttr2) and in a block. From jlog: where t1.col1 IN (?, ?) DEBUG JRJdbcQueryExecuter,http-48080-7:305 - Parameter #1 (LoggedInUserAttributeValues[0] of type java.lang.String): Value1a, Value1b DEBUG JRJdbcQueryExecuter,http-48080-7:305 - Parameter #2 (LoggedInUserAttributeValues[1] of type java.lang.String): Value2a, Value2b, Value2c Is there a way to use the mentioned Parameters or there are others which allow the same as LoggedInUserAttribute_<attribute name> does but which are of collection type so that they can be used with an $X . Or can you think of another way to solve this problem? Many thanks!

Hello, I have a report which has 9 Input controls, 7 from them are cascaded. This report is running with acceptable performance when JasperReports Server CP 4.0 is accessed with Firefox (3.5 or 5) or Chrome. With IE 7 it is very slow, the mouse moves slow and the cascading IC react very slow: script loading the ICs?. After a while, I get the error message: "A script on this page is causing Internet Explorer to run slowly". Is it possible to get a better performance via configuration? Ideally in JR-Server since I have no direct access to the users' PCs. BTW: in my PC I add the registry entry as described in http://support.microsoft.com/kb/175500/en-us and this entry, eliminate the error message which pops up after a while "... causing IE to run slowly" but the performance stays equally bad. Thanks in advance for any ideas.

in case someone gets a similar error: this one was the input control query which returned a "null" within the results. An extention in the where clause: "... and t1.col1 is not null" solved the problem. Post Edited by terco at 08/02/2011 10:57