pinkman

When a user logs into JasperServer, they can see the folder 'labels' in the Display Name column. But when they navigate down to actual reports they see the report 'names' in the 'Display Name' column instead of the label. Is this a bug? Have a missed something, and are there options somewhere to select which columns to display?

I am in the process of converting our business from Crystal Reports to iReports/JasperServer. One thing holding us back a little is lack of user training. The training offered seems to be more from a programmers POV, when really our business users just want to know the ins and outs of creating reports (with advanced topics like crosstabs/sub-reports etc) and deploying them to JasperServer. Has anyone come across good web based training for this? Or perhaps there is a really well put together tutorial I could take our users through myself? Any feedback appreciated thanks :)

In order to make my input controls re-usable, I want to store them in a separate folder to the reports themselves. I have linked a trial report to a input control in another folder. When I run the report it comes up with the correct list of values. So far so good. But, when the report runs the parameters don't get passed to the report. They come through as 'null'. It is likely the name I am looking the parameter up by. Currently I am looking it up by it's actual name, e.g.: $P{name}. Does this need to be something special like '$P{repo:/path/to/input_controls/name}'? I am lost here, so someone please point out the obvious :).

Kia Ora, I have changed the password storage from plain text to DES via the applicationContext-security.xml file. This is working fine. I am wondering what other options there are for the 'cipherTransformation' property other than 'DESede/CBC/PKCS5Padding'. In particular I am wanting to store the passwords as an MD5 hash. I have looked through the JS ultimate guide, and the install guide and searched forums but I haven't come across anything. Apologies if I am missing the obvious here :). Thanks, Simon.

Hi Teodor, Thanks for taking the time to reply. I understand your concerns, and I too agree that complicate logic should reside somewhere outside of the report itself. For the most part I think logic can be tucked away into the SQL. Unfortunately getting our business users to create stand-alone Java files is out of the question for us; they are business users after all and not developers. For what we need it for it would be overkill anyway. My problem is that I am trying to convince them to switch from Crystal Reports to Jasper. I have solid experience with Crystal, and a bit of experience with BIRT; both of which allow general scripting for the report functions, see: http://www.eclipse.org/birt/phoenix/project/notable2.0.php#jump_13 . Our users will not be writing overly complex logic in the functions, but really need simple things like case statements and if-else statements. I am training our users now, and as they get used to it they are finding the lack of power of the Jasper functions frustrating - they are loving everything else :). In the long run though, from my experience I believe making this change would help migrate more people onto Jasper and away from Crystal and other products. Kind Regards, Simon.

It seems to be the way the report is compiled, it is compiled to use an inline statement, for instance: Code: value = (java.lang.String)((true ? "true" : "false" )); Knowing this, you can hack the expression to make it more scriptable like so: Code:[code] ""«»); boolean asd = true; if (asd) value = "www"; else value = "asd"; ("" Just an observation :) I have raised a feature request: http://jasperforge.org/sf/go/artf3040

Thanks for the reply Pedja. In that case, does anyone know of any work being done to make the functional language a bit more user friendly/powerful? My business users will be happy so long as I can tell them usability will improve. For now, I will recommend that they switch the language to Groovy, which helps a bit as most of my users don't understand OOP much, if at all. It would be nice if we could harness the full power of Groovy and use proper if else statements. It does seem to me to be the biggest shortfall of Jasper. If there isn't any work being done on it, is there somewhere I can report a request? There is even a possibility I could offer my programming services.

We are upgrading from Crystal to iReport. One of the main hurdles is learning the syntax for field functions (not all users are Java developers). So far it looks like the Crystal syntax is easier to use, making it the only good thing about Crystal IMHO :). In particular, is there a nicer way to do if/else and case statements other than what is recommended here: http://www.jasperforge.org/index.php?option=com_joomlaboard&Itemid=&func=view&catid=9&id=12491#12491 . I would like to get away from having to make users do it in SQL, as case statements in SQL are often vendor specific. And using the (true):then?else syntax gets unwieldy when you have more than a few different options. Thanks for reading this, and any ideas would be appreciated :). Simon. Post edited by: pinkman, at: 2008/02/19 02:09 Post edited by: pinkman, at: 2008/02/19 02:10 Post edited by: pinkman, at: 2008/02/19 02:11