darth_fader

This would be great!

If using Jaspersoft Studio, simply highlight the field via the GUI editor, and then update the 'Pattern' in the text field properties. You can specify whatever precision you'd prefer.

Looks like you're getting some unwanted content in csv output, probably from a page header or title band - look at the 'exclude' optoins in the jasper config reference: http://jasperreports.sourceforge.net/config.reference.html#net.sf.jasperreports.export.{format}.exclude.origin.{suffix}.{arbitrary_name} You can exclude items on a per format basis by key (remove on a per element basis) or band (remove entire band) for a specific format. The documentation is a little lacking but a simple google search will get you what you're looking for - <property name="net.sf.jasperreports.export.csv.exclude.origin.band.pageHeader" value="pageHeader"/>

If you're working with an older version of Jasper Server (6.2.x or older) you'll need to enable using stored procedures - steps are detailed here: https://community.jaspersoft.com/wiki/how-execute-ms-sql-stored-procedure-jasperreports-server If you're working with version 6.3 plus, no changes are needed. If this doesn't address the issue you're expriencing, post your jrxml. Is this the first report resource you're publishing that references a stored proc?

Haven't done this before, but I would simply export the server contents from the linux version and import them into the windows version - you can do this through the server's web interface or the command line. The web interface is self explanatory, just 'view repository' right click somewhere in that directory, and click 'export'. Here are some instructions on the command line version of that process: https://community.jaspersoft.com/documentation/jasperreports-server-administration-guide/v550/import-and-export-through-command-line I'd keep it simple and use the web based approach, although the command line does provide additional options.

Would like to confirm that the Jaspersoft for AWS product in the AWS market place does not include additional licenses for dev/qa etc. as would be the case with a traditional Enterprise license purchase. I'm assuming I'd have to purchase separate instances for any additional environments (dev/qa/etc.)? Makes sense, each EC2 container is only going to support one instance of Jasper Server, and if I require more than one instance (for development, qa, production) I'd have to purchase/launch additional instances? Any info is appreciated!

Is it possible to customize Jasper Server itself on the AWS version? I'm not certain if this is possible as it's packaged as an AMI (amazon machine image). I'm not looking to do anything advanced, just want to white label the system. However, from a technical perspective, it's all the same. I'd need to modify Jasper Server files. I'm assuming this is possible, but want to verify before committing to that solution. Has anyone had experience customizing AWS JS, or can confirm wether or not it's possible? Thanks!

Add your subreports to the summary band. You will need a stub query in your parent report (select 1 from TRUE etc. - that depends on what type of db you're hitting), or a query that always returns records. An alternative to that stub query, you may be able to just set the report property - whenNoDataType="AllSectionsNoDetail" at the report level to always render your summary band.

Can you post the stack trace from the server log?

In parent report, pass that oracle connection parameter to your subreport right below where you would pass sub report parameters, as follows: <subreportParameter name="orgId"> <subreportParameterExpression><![CDATA[$P{orgId}]]></subreportParameterExpression> </subreportParameter> <subreportParameter name="personId"> <subreportParameterExpression><![CDATA[$P{personId}]]></subreportParameterExpression> </subreportParameter> <connectionExpression><![CDATA[$P{oracleConnectionParam}]]></connectionExpression> You don't need to do anything else in the subreport itself. Just make sure oracleConnectionParam is defined as type java.sql.Connection in the parent. Connection Expression is available in Jaspersoft Studio GUI as well if you're not sure how to define that for the subreport element

Have you tried the JDBC jar for Big Query? https://cloud.google.com/bigquery/partners/simba-drivers/ I'd suggest adding that in to your environment (Jaspersoft Studio or Jasper Server) and test it out with some basic queries. https://cloud.google.com/bigquery/partners/simba-drivers/ This should give you basic SQL support agianst a Big Query data source.

+1 Shertage - this is most likely related to a font substitution occuring via the JVM, a problem that can be elminated via font extensions A work around I use is to make the text element 1px in height and set the text fields to stretch with overflow - eliminates the sporadic white spice that can occur without the need for a font extension. However this approach makes the report template harder to maintain because then you're working with 1px height elements in Jasper Studio.

Beyond the roles approach suggested above, the only other option I can think of, if you wanted to support some kind of 'user delegate' that would allow one user to inherit any/all permissions available to a set of users, is to create a custom security mechanism via Spring. This is easier than you might think, Jasper Server uses Spring Security as it's default security provider, and they've made it very easy to customize and/or extend that functionality.

you can use if /else conditionals in a variety of places, including any place that can be defined with an expression (variables, parameters, text fields, printWhenExpressions). If/else expressions can defined using ternary operators in the form of ( true-false expression ? true expression : false expression). Jasper Studio also has an IF/ELSE expression wizard that can be used to define this.

You can create a separate jasper reports user for each client database, then add user attributes for each user that specify the db, port, credentials, etc in the JDBC connection on jasper server. This is definitely doable if you can authenticate with a different user to Jasper Server depending on the client in use. Example: Client A authenticates to JasperServer with User A, with User A attributes defined that connect to Client A's database. https://community.jaspersoft.com/documentation/tibco-jasperreports-server-administration-guide/v610/attributes-data-source Using the REST client with this approach is a non-issue, the REST client would specify the Jasper Server user to authenticate with. Hope this helps.

You can always pass that whole json to a java layer, and create lists of java objects that correspond to your reports hierarchy (parent object list for parent report, child object list for child report) - then use java objects as your datasource accordingly. Will require a little json parsing, and a little coding, but neither would be that complicated. Then you can get the output set the way you want it.

That's a really good question. And valid. I think this may not be readily available within Jasper as the entire result set would have to be held in memory until all variations on displaying the data were "filled", and this would in essence bypass jasper's optimization for filling reports efficiently. Not a real problem on small result sets, but holding them in memory wouldn't be scalable.

If you want to restrict access to the UI, and are just using Jasper to serve up resources, can't you use the REST API and use proper permissions on resources to prevent repo browsing?

Add a line element to your report, and dynamically display it using the "printWhenExpression". You can use a dotted line by looking at the "linePenStyle" options

Jasper has tons of built in support for dynamic date ranges, this is a common problem with a common solution. In fact, Jasper Reports has a specific "DateRange" type that can do a lot of the heavy lifting for you. Handles things like "Date +1 week" etc. https://community.jaspersoft.com/wiki/how-use-relative-dates-tibco-jaspersoft-studio-report

post some code snippets, let's see what you're working with

Here's what I recommend. Via the Outline view, select the column header or row header you want to adjust, and then once the row or column is highlighted on the design editor, you can drag the size to meet your needs. It comes with practice, and I'll admit it's not intuitive. Reordering row groups, or adding/removing a measure is definitely a pain, at times I've had to recreate the crosstab from scratch. Best advice I can give is to get your columns, rows, and measures in place via the wizard, and get them how you want them before you do any extensive formatting or manipulation on those objects.

I'd recommend creating each "page" in a subreport, each with size 8.5X11, then including those in a parent report and allowing each subreport to expand as necessary. Alternatively, you could add three detail bands to one report, one for each page. It will be trial and error to see what works best.

I've seen mixed answers on the subject, so I'm hoping an authority on the project will chime in: can we safely use subreports in page footer bands? My scenario is branding: I want to brand the footer with organization metadata, and just like with html, the footer content is redundant for most/all of my reports. Subreports are the closest I can come to templating in jasper. I've tested and it seems to be stable, I'm just wondering if there are any issues that could arise that I'm not aware of? This particular subreport has a real query with fields etc, but there is a one record limit and fields associated with that record will always be displayed in two lines - in essence it's a fixed height. I can see how issues would arise if we tried to put a standard detail band with page after page in the footer region. But this is not the case. I'd also like to take the same approach with the page header, so a better way to ask this question may be, "Are there report bands we should avoid using sub reports in"? Thanks

I had to sit through some updates after the initial install for my palette window to populate. Thanks hozawa!