
In summary, by adding a second parameter to the Jasper Report that performs a conditional string replacement, we can mimick the behaviour of the ADempiere Report Engine and ignore null values as don't care conditions. Otherwise the condition will be true, which will result in no filtering at all, just like in ADempiere's report engine. When you pass the report a value, the value will be used, becoming the where condition for example c_bpartner_id = 1234567.

#Jaspersoft studio query parameter not found how to
You should already understand how to create a Report and Process with parameters in ADempiere and link it to a Jasper Report which uses parameters. You will need to have a report in your database that uses Jasper Reports and that accepts parameters from ADempiere. To fix this, we need a way to communicate the intention that a null value means "I don't care". If you create a parameter in ADempiere to select a date and a matching parameter in your Jasper Report and leave the date blank, the Jasper Report query will look for matches where the date column is null - probably not what you intended.

For example, you may have a report with a date field and you would like the option of selecting a specific date or all dates. This article explains how to create a parameter in a Jasper Reports which will allow you to select specific records or all records in the underlying data. (The original HowTo article was written by by Mario Calderon.) This Wiki is read-only for reference purposes to avoid broken links.
