Skip to main content

iReport Default Date Parameter

If you want to set a default date for a jasperreports parameter, you can enter the following in the default value expression of the parameter.

new Date()

However, if you wanted the default to be relative from today, for example, 3 days ago, you will need to do go outside of the standard java date libraries (Date, Calendar) because JR parameter does not allow you to have multiple statements. You can write your own utility package or you can use Joda, a replacement library for the JDK date and time library.

To use Joda in iReports, you need to extract the jar file and add it to Options -> Classpath. You may also drop the jar file in iReports' lib directory. You will also need to add this library to your application or report server.

For setting a default date 5 days prior from today, use this:

new org.joda.time.DateTime().minusDays(5).toDate()

or this if you want the time part set to the beginning of the day:

new org.joda.time.LocalDate().toDateTimeAtStartOfDay().minusDays(5).toDate()

or if you want the parameter to be relative to another parameter:

new org.joda.time.LocalDate($P{DateParam}).toDateTimeAtStartOfDay().minusDays(5).toDate()

Joda has other methods to get a relative date: minusWeeks, minusMonths, minusYears, plusDays, plusWeeks, plusMonths, plusYears. I think you can also use Groovy to write an expression to get a relative date but that's for another time. It would probably be as simple as new Date() - 5. Post a comment if you came up with a better way.

Comments

Winthropian said…
Nice.
Do you know of a neat way to print a calendar in iReports? The goal it to print a calendar with various dates filed in based on data in tables.
Cheers,
Rich
Erik said…
As of now you can use Groovy for an expression as well.

new Date().plus(7) //7 days from today
Unknown said…
NIce and informative. Do you know how it would works to display milliseconds in the difference between two dates? I would really appreciate if you please let me know about it.

Best regards.
Anonymous said…
Hi superb website! Does running a blog like this require a lot of work?
I have absolutely no knowledge of coding however I had been hoping to start my own blog soon.
Anyhow, should you have any recommendations or techniques for new blog
owners please share. I know this is off topic nevertheless I simply needed to ask.

Appreciate it!

Take a look at my web site :: weight loss
my website > weight loss
Anonymous said…
It's a pity you don't have a donate button!

I'd certainly donate to this outstanding blog! I guess for now i'll settle
for bookmarking and adding your RSS feed to my Google account.
I look forward to fresh updates and will talk about this site
with my Facebook group. Chat soon!

Feel free to visit my blog post http://gohima.com/

Popular posts from this blog

Migrating Moniwiki to MoinMoin

I had been using Moniwiki for our company for a while because the installation was quite easy as it was PHP based. However, I found out that document versioning didn't really work. It may have been a configuration issue but I took this opportunity to take a look at MoinMoin, as it was being used by Ubuntu and looked well supported. The server was running Debian stable and MoinMoin was in the repositories. Installing was simple using aptitude. Configuration was a bit more involved as it required copying and editing files. The new wiki site was pleasantly more responsive. The next task was to move the data in Moniwiki to MoinMoin. Upon inspecting the data repositories, I realized that Moniwiki stored the data in individual files with the WikiWord as the filename while MoinMoin organized that data with the WikiWord as a directory with the actual content under the revisions directory. I cooked up a quick script to migrate the data. I also ran the previous file through a 'tr' to...

CI/CD for .NET Core

If you have a .NET API that you want to containerize, here are the steps to prepare it. Create docker image Push to repository Setup ECS The TLS 1.0 option is needed if your SQL Server database does not support TLS 1.2. The recommended option is to update your database to the secure protocol. You may also change sdk and aspnet version to 5.0 if you haven't updated to 6.0 yet. This Dockerfile uses a multi-stage build to get an optimal image size. Dockerfile FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build-env WORKDIR /app # Copy csproj and restore as distinct layers COPY *.csproj ./ RUN dotnet restore # Copy everything else and build COPY . ./ RUN dotnet publish -c Release -o out # Build runtime image FROM mcr.microsoft.com/dotnet/aspnet:6.0 WORKDIR /app # Enable TLS 1.0 RUN sed -i 's/DEFAULT@SECLEVEL=2/DEFAULT@SECLEVEL=1/g' /etc/ssl/openssl.cnf RUN sed -i 's/MinProtocol = TLSv1.2/MinProtocol = TLSv1/g' /etc/ssl/openssl.cnf RUN sed -i 's/DEFAULT@SECLEVEL=2/DEFAULT@...