jojopaderes

I'm using JasperServer Pro 3.1 by the way. I also tried using the code snippet with version 3.5 but still the list object does not include the inherited permissions of a particular repository folder.

I'm figuring out how to retrieve the list of object permissions for a repository folder. Here's the code snippet that works so far: objectPermissionService.getObjectPermissionsForObject(null, repositoryService.getFolder(null, "/report/child_folder)); The list object returned by the getObjectPermissionsForObject() method, however, does not include the inherited user/role permissions from the parent folder. Is there a way on how to get the inherited object permissions for a repo folder?

I'd like to know if it is possible to modify the folder permissions using web service. I have read already the JasperServer Web Services Guide document but couldn't find any references on how to modify the folder permisisons using web service. Thanks!

Please ignore the issues I listed at post #53340. These behaviors were caused by activating the "Set these values as defaults when saving report." checkbox at the report options popup shown when creating a new adhoc report (see attachment).

That's good news indeed! Thank you for working in this issue really fast! There are also a couple of issues I found with the multi-select input control (when used in the adhoc report) even after applying the workaround I came up (see post #53103) 1. Changing the parameters using Report Options does not refresh the data displayed at the adhoc report preview. 2. Selected report parameters for multi-select input control does not get saved. I hope these issues were also fixed with the upcoming release. Post Edited by Jojo Paderes at 03/15/09 01:52

I have managed to do a test using MySQL and there was no exception thrown. I don't see the JDBC exception complaining about the mismatch with the IN parameters and column data types, instead, JasperServer simply don't return any data results. Interestingly, I can execute the following sql code in MySQL and PostgreSQL without any problems (directly executed using a DB client app), but executing this query in JasperServer fails: SELECT * FROM product WHERE product.product_class_id IN ('1','2'); Using andrewsok report jrxml example, launching the report designer will produce the following sql code and logs respectively: WHERE 1=1 AND ( product_class.product_family = 'Non-Consumable' OR 1 = 0 ) AND product_class.product_class_id IN (1, 2, 3, 4, 5) DEBUG JRJdbcQueryExecuter,Thread-15:257 - Parameter #1 (ProductClass[0] of type java.lang.Integer): 5 DEBUG JRJdbcQueryExecuter,Thread-15:257 - Parameter #2 (ProductClass[1] of type java.lang.Integer): 4 DEBUG JRJdbcQueryExecuter,Thread-15:257 - Parameter #3 (ProductClass[2] of type java.lang.Integer): 3 DEBUG JRJdbcQueryExecuter,Thread-15:257 - Parameter #4 (ProductClass[3] of type java.lang.Integer): 2 DEBUG JRJdbcQueryExecuter,Thread-15:257 - Parameter #5 (ProductClass[4] of type java.lang.Integer): 1 So far so good. The ProductClass collection contains the correct object types which are of Integer class. Running the adhoc report, this is the log output now: WHERE 1=1 AND ( product_class.product_family = 'Non-Consumable' OR 1 = 0 ) AND product_class.product_class_id IN ('1', '2', '3', '4', '5') DEBUG JRJdbcQueryExecuter,Thread-16:257 - Parameter #1 (ProductClass[0] of type java.lang.String): 5 DEBUG JRJdbcQueryExecuter,Thread-16:257 - Parameter #2 (ProductClass[1] of type java.lang.String): 4 DEBUG JRJdbcQueryExecuter,Thread-16:257 - Parameter #3 (ProductClass[2] of type java.lang.String): 3 DEBUG JRJdbcQueryExecuter,Thread-16:257 - Parameter #4 (ProductClass[3] of type java.lang.String): 2 DEBUG JRJdbcQueryExecuter,Thread-16:257 - Parameter #5 (ProductClass[4] of type java.lang.String): 1 Again, take note that the collection now contains String objects instead of Integers. Using PostgreSQL database and driver an exception will be thrown from JasperServer. Upgrading the PostgreSQL driver does not help either. Back in JasperServer 2.1 the object types in the collection remain consistent, always Integer if the input parameters are of int type. Post Edited by Jojo Paderes at 03/10/09 04:57 Post Edited by Jojo Paderes at 03/10/09 04:58

Thank you andrewsok for helping out checking this issue! Another thing that confuses me with this multi-select input control bug with adhoc reports is that I don't have this problem with non-adhoc reports. I think there's something else going on with the adhoc report that causes it to generate incorrect SQL IN parameter codes. I came up with a workaround for the SQL IN parameter issue caused by the multi-select input control in the adhoc report. Instead of using the $X{} built-in function of JasperReports, I used a Java code snippet to generate a CSV value for the collection input values. Please see the code section for the snippet. The code snippet works well for resolving the IN parameter sql code problem, both for adhoc and non-adhoc reports. The new problem I'm struggling right now is that when changing the report options for the adhoc report, the report data displayed does not get updated. This is not the case with non-adhoc reports. Code:...<import value="org.springframework.util.StringUtils" />...<parameter name="MultiSelectInputValues" class="java.util.Collection"/><parameter name="InputCsv" isForPrompting="false"> <defaultValueExpression><![CDATA[ $P{MultiSelectInputValues}.size() > 0 ? StringUtils.collectionToCommaDelimitedString($P{MultiSelectInputValues}) : "NULL" ]]></defaultValueExpression></parameter>...<queryString><![CDATA[sELECT foo_columns FROM foo_tableWHERE int_column in ($P!{InputCsv})]]></queryString>

Thanks andrewsok for providing the sample report. I was still able to replicate the problem that I had before using the sample you gave. I'm attaching a storyboard on how I was able to replicate the problem. Here's the where clause snippet that was captured when I ran the adhoc report. Looking at the IN parameters, it's obvious that the values are specified as character/text types (enclosed by the single quotes) which is clearly a mismatch with the product_class_id integer column: WHERE 1=1 AND ( product_class.product_family = 'Drink' OR 1 = 0 ) AND ( product_class.product_class_id IN ('5', '4', '3', '2', '1') ) Post Edited by Jojo Paderes at 03/09/09 16:19 Post Edited by Jojo Paderes at 03/09/09 16:21

Thanks for replying Sherman. I'm using a multi-select input control for the report.

This works well with the sample reports that comes with Jasper Server, however, when adding more input controls to these sample reports the new controls don't show up in the "Special Content > Single Report Controls" folder. I'm using the sample Freight Report that comes with JS 3.1 and tried adding some input controls (locally defined) to it. When I tried creating a dashboard for this report, I couldn't find the new input control under the Single Report Controls. I'm not sure if I did the right approach. If not, I'd like to know the right way of adding input controls to an existing report so that these controls will show up at the "Special Content > Single Report Controls"when creating dashboards. I posted an inquiry about this a few days ago, see http://jasperforge.org/plugins/espforum/view.php?group_id=112&forumid=102&topicid=52218 mryzhikova Wrote: Hello! I assume you are using Professional edition of JasperServer? If yes, then here is how you add input controls: When you create dashboards, you have to choose reports that have input controls defined. Once you added that report to dashboard designer -> dashboard selector, predefined inputs will automatically appear under “Special Content -> Single Report Controls” folders. Then you can choose any of those inputs and add to dashboard selector. Hope this helps! Good Luck! Post Edited by Jojo Paderes at 02/22/09 02:20

I'm trying to figure out how to add single report controls for a dashboard report. I'm using the sample Freigh Report that comes with JS 3.1 and tried adding some input controls (locally defined) to it. When I tried creating a dashboard for this report, I couldn't find the new input control under the Single Report Controls folder at the Available Content pane. Am I missing some proper steps on how to add a new input control that can be used when creating a new dashboard? The Jasper Server user guide didn't gave much detail on this, so I'm completely clueless.

For some reason the forum site is not allowing the attachment to be uploaded. The attachment is a zip file containing logs and xml data.

I just upgraded to Jasper Server 3.1 and bumped into some problems using the multi-select input control with an adhoc report. Running the adhoc report will always end up with an SQL exception. The exception has something to do with the mismatched data types used in the WHERE IN sql clause. This only happens after with JS 3.1. The adhoc report with multi-select query works well in JS 2.1 Using the sample FoodMart sample that comes with JS 3.1, I modified the SuperMart Products adhoc topic and added a new multi-select input control that fetches the list of product_class_id values from product_class table. I also modified the query string of the topic by using a $X{IN, column_name, collection} function that will take in the multi-select query values. After completing all the necessary configurations for the adhoc topic, I launched the adhoc report page, selected some entries in the multi-select input control, added a few columns at the adhoc report canvass then clicked on "Run" button. Instead of getting the report display, I got an exception page instead. Please refer to the attachment for the stack trace. One thing I noticed with the problem I encountered is that the exception only happens when I select multiple entries from the multi-select input control. Another interesting observation is the changing object type inside the input control collection when fed to the Jasper Report template. Before running the adhoc report (that's after selecting some entries from the multi-select input control), this is the log output: WHERE 1=1 AND product_class.product_class_id IN (1, 2, 3, 4, 5) DEBUG JRJdbcQueryExecuter,Thread-15:257 - Parameter #1 (ProductClass[0] of type java.lang.Integer): 5 DEBUG JRJdbcQueryExecuter,Thread-15:257 - Parameter #2 (ProductClass[1] of type java.lang.Integer): 4 DEBUG JRJdbcQueryExecuter,Thread-15:257 - Parameter #3 (ProductClass[2] of type java.lang.Integer): 3 DEBUG JRJdbcQueryExecuter,Thread-15:257 - Parameter #4 (ProductClass[3] of type java.lang.Integer): 2 DEBUG JRJdbcQueryExecuter,Thread-15:257 - Parameter #5 (ProductClass[4] of type java.lang.Integer): 1 Running the adhoc report, this is the log output now: WHERE 1=1 AND product_class.product_class_id IN ('1', '2', '3', '4', '5') DEBUG JRJdbcQueryExecuter,Thread-16:257 - Parameter #1 (ProductClass[0] of type java.lang.String): 5 DEBUG JRJdbcQueryExecuter,Thread-16:257 - Parameter #2 (ProductClass[1] of type java.lang.String): 4 DEBUG JRJdbcQueryExecuter,Thread-16:257 - Parameter #3 (ProductClass[2] of type java.lang.String): 3 DEBUG JRJdbcQueryExecuter,Thread-16:257 - Parameter #4 (ProductClass[3] of type java.lang.String): 2 DEBUG JRJdbcQueryExecuter,Thread-16:257 - Parameter #5 (ProductClass[4] of type java.lang.String): 1 Take note of the changes both with the generated sql where clause query and the object type of the parameters inside the collection. From Numeric/Integer type, these were changed to Strings. This will then cause the following exception in the database: org.postgresql.util.PSQLException: ERROR: IN types integer and character varying cannot be matched Post Edited by Jojo Paderes at 02/11/09 17:44

There seems to be some inconsistency with regards to the accessability of /adhoc/temp folder when used for saving adhoc reports and setting the target folder for scheduled reports. When saving adhoc reports, the /adhoc/temp folder is not displayed in the folder tree. Using the scheduler and specifying the target folder will allow the user to use the /adhoc/temp folder for saving scheduled reports. I think this poses a security concern wherein we don't want scheduled reports to be stored at the /adhoc/temp folder. The adhoc report does prevent users from savings reports at the /adhoc/temp folder, however, this is not the case with the report scheduler. It's not an option to impose a read-access right on the /adhoc/temp folder as this will cause the adhoc report feature to fail. One possible workaround is to hide the /adhoc/temp folder from the list of available target folders when scheduling a report. The question is how to control the list of available target folders at the report scheduler. scheduler_.png attachment shows the /adhoc/temp folder from the list of output folders for the scheduler adhoc_repo.png attachment shows the list of folders when saving an adhoc report. I made a mistake with the label in the image. It should be "/adhoc/temp folder is not seen here". Post Edited by Jojo Paderes at 02/11/09 16:09

lucianc Wrote: I see now that there already exists a feature request for this (see artf2176). Regards, Lucian The link you gave seems to be broken. Can you provide the working link that would point to the feature request? Thanks!

Duplicate post. See next entry instead. Post Edited by Jojo Paderes at 01/29/09 10:03

Are there any updates if Jasper Server 3.1 release supports the LoggedInUser within a Single Select Query input control?