manshack_one

Turns out there was null data sneaking into the calculation and Groovy wasn't sure how to handle it. Changed my logic up to check for that situation first and now i'm good to go.

I have a report that has an issue with evaluating a few fields with an expression like this one after upgrading from 6.0 to 6.3. In 6.0 there was no issue with this statement. I get confused on how Groovy and Java are intermingled when creating expressions. There are a few google results that talk about how after groovy 2.4 they began checking overloaded methods more closely but I can't make any sense of what it means. This is a pretty straightforward shorthand expression for an if-then situation. Any suggestions on how to write this expression so that it doesn't have an issue being resolved? Expression: ($F{dental1}!=null || $F{dental2}!=null || $F{dental3}!=null)? ($F{dental1}+$F{dental2}+$F{dental3})/3:null Error:Caused by: groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.lang.Long#plus.Cannot resolve which method to invoke for [null] due to overlapping prototypes between:[class java.lang.Character][class java.lang.String][class java.lang.Number]

How would I go about upgrading ONLY the PostGre install that is bundled with JS 6.0.4? I realize I could update the entirety of JS to 6.7 but right now I just need the PostGre install updated. Thanks in advance....

Ok, would you happen to have a link to a write up for how to do a binary file update versus a full blown installer update? My biggest concern is that something functionally might change and since jasperserver was built with 9.0 in mind it might break how the program functions.

Anyone had to do this? My network admins ran a sweep and figured out the bundled Postgre with JS 6.0.1 is a bit out of date. Can you just update Postgre without major issues?

I switched to using $P!{} and passed in a literal "(1,2,3)" in my URL and used a string input control on Server and changed my report query to something like "where r.attendee IN $P!{parameter_name}" and it works fine now. Thanks for the reponses regardless.

I'm following along with you but I'm at this point in studio creating the input control. I've named it the same as the parameter in the report itself. However, since this input control is not going to be visible (because I want to use the http repository api) the user will never have the option to enter the values. The values will come from the URL string I'm building inside my application. So what do I use at this point to get Server to let me use a multiselect without creating the list of values at this point?

How do I create the input control on JasperServer since the input is in the URL? There isn't a collection data type in the repository resources. If i set it to multi-select then you can't save the control without listing a set of values.

With JasperReports you only get to run one query per report. Exceptions to that would be subreport elements or writing the selects in code and adding a bean to the report to run it. I generally find it's easier to build my query using a query editor outside of JasperStudio and view my results there. Once I know I can build one query to pull everything together into one large dataset then I'll move it to JasperStudio and copy the query in. Then you can decide what you're going to filter on or group. Hopefully that makes sense.

Are you able to connect to your JasperServer instance from within JasperReports Studio? Perhaps you could try creating your datasource there instead using the Repository Browser. If you're still unable to save the datasource then Studio might give more of an error message to work with. Also, depending on how you did your install for JasperServer there might be a security permission issue keeping the application from modifying the database. Perhaps double check your roles in the database itself.

I'm trying to run a query in my report that includes a "where columnname IN (1,2,3)" by using "$X{IN,columnname,parametername}". I created a parameter in Jaspersoft Studio as a collection. Once I publish the report to JasperServer then I know I'm supposed to create an input control on the server that matches the name of the report parameter. My problem though is from what I've read I'm supposed to create a multi-select input control however when I'm creating the control the dialog wants you to select a data type or list of values right then and I don't know what to tell it to use. Also, what format should my string be in that I'm passing to the $X{} parameter in my URL report call? (1,2,3) or leave off the parenthesis? I can build the string pretty much any way I need to. Right now everything I throw at it is not being recognized so the query builder uses 0=0 for my $X{IN} clause and pulls everything in the tables.

nevermind....should have googled some more. I had to uncheck the "Visible" property in the input control in the repository so it wouldn't prompt me for the value. Works just as intended now.

I've written a report that has an input control. I'm trying to run the report using a URL according to the community documentation which is built dynamically so the classScheduleId is added on the fly. In Studio I've turned "Is For Prompting" to false for the parameter yet when I execute report via URL I'm still presented with the input control prompt on the server with this value pre-populated. What I need to happen is the report just get generated and to view the resulting PDF. I'm running JasperServer Community 6.01 and Studio 6.0.4. http://<servername>:8088/jasperserver/flow.html ?_flowId=viewReportFlow&standAlone=true &_flowId=viewReportFlow&ParentFolderUri=%2FITD&reportUnit=%2FITD%2FClassRoster &j_username=jasperadmin&j_password=<password> &classScheduleId=145 &output=pdf

Maybe I could force my query results to contain empty rows........ Consider that I'm trying to build a sign in sheet for a class. If a class has a capacity of 20 seats (the max I expect) then I need 20 rows for people to sign in on. However, if people have already signed up then I want to pre-populate their names. So how would I force empty rows in the query? tblClassSchedule.classCap is the number of rows I need to generate. select *, (select tblUsers1.userName from tblUsers1 where tblClassSchedule.classInstructor = tblUsers1.ID ) as instructorNamefrom tblClassSchedule, tblClassRoster, tblClassInfo, tblUsers1, tblBranchwhere tblClassRoster.classID = tblClassSchedule.IDand tblClassInfo.ID = tblClassSchedule.classInfoand tblClassRoster.attendeeID = tblUsers1.IDand tblBranch.ID = tblUsers1.userBranchand tblClassSchedule.ID = $P{classScheduleId}

hozawa

KKriplani, If you set a page break like that, what happens if report count is less than 10? Would it repeat the detail band (which is what I'm trying to force the report to do)?

I'm building a report that's a sign in sheet. I need to force the number of rows in the report to be equal to the capacity of the class (I have the class capacity as a field so I can reference it). How do I force the detail band to print blank rows equal to this number? For example: A class has a capacity of 20 students but only 10 have signed up. When the sign in sheet is generated it should include 10 rows with student data and 10 rows without to leave room for handwritten entries on the printed copy. I considered the print when expression but I'm not sure how to say "print rows until 'i' is equal to capacity like you would in a loop.

Are there any options with the JasperServer product or in JasperStudio to create ADA compliant PDF's with proper tag structures? You can already allow adobe to infer a reading order naturally but what if you need another order? We need to output Purchase Orders which obviously isn't a problem to ingest the data and output the files but the output PDF needs to have a certain reading order. Anyone have any experience with that?

I use Heidi but it would be nice to see it in the report designer so that your parameters would be in place. When I copy the query to Heidi I have to go through and replace all the parameters to static values.

Need to know how to view the results of my report query because I'm having grouping issues. I just need the raw result set from the query much the same as you get with the preview data option in the query screen. Only, in the query screen when you preview it doesn't ask for the parameter values so I can't see the data. Is there a logging setting somewhere that can be set? I'd like to just see the results in the iReport output window if possible so I can compare what's on the report with whats in the actual data.

bump is there a way to run the main query, then have another dataset run a query against those results?

I'm needing to go from 3.7 on Server A to 4.0 on Server B. Server B was installed using the WAR file install and buildomatic scripts for mysql. Can I still just export on Server A and import on Server B? Or do I have to do something in between?

In order to move my 3.7 repository of reports, datasources, etc. to 4.0, do I have to run an upgrade script in place before doing the export script? Or will the 3.7 data import into the 4.0 tables without modification?

Well it wasn't easy but we managed to get it installed on Glassfish 3.1 with MySQL 5.5. Took a lot of googling and editing of files but it's in there and works.

I've downloaded jasperreports-server-cp-4.0.0-bin and I'm about ready to run the install. What I need to be sure about is that the install in this version of the release will in fact install the files onto an exisitng glassfish install and mysql install. When the default_master.properties files started asking for directory path info it made me think it might be trying to install from scratch like with the regular installer.