nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Inserting Input Paramaters in Dataset within BIRT

warren_marsha@hotmail.com

Hi All,
 
I'm using Oracle...
 
I have a dataset that requires capturing data for the previous month.
 
The user can enter current month, Month = 01 and Year = 2016, as input parameters.
 
I'd like to be able to take the input from the user and convert the string values to to_date(input parameters, 'MM/YYYY'), but I don't believe I'm using the correct syntax.
 
Within my dataset I currently have ...
where date_field < to_date(' " + params[Month] || '/' || params[Year] + " ', 'MM/YYYY')
 
Is this the correct syntax for concatenating the input parameters and formatting them as dates ?
 
Thanks

Find more posts tagged with

Comments

micajblock

What database are you using? What version of BIRT?
 
Also month/year is not a date.

warren_marsha@hotmail.com

I'm using Oracle.
 
BIRT version 2.5.2
 
Correct... Month/Year is not a date. I need to convert the input string value params[Month] = '01' and params[Year]='2016' to a to_date format of 'MM/YYYY', because I need to compare the values to a date value.
 
I need to know what the syntax is for using input parameters in the datasets within BIRT.
 
I currently have ... where date_field < to_date(' " + params[Month] || '/' params + " ', 'MM/YYYY')
 
Is this correct syntax if I place it in my dataset within BIRT?
 
Thanks

micajblock

<blockquote class="ipsBlockquote" data-author="warren_marsha@hotmail.com" data-cid="144693" data-time="1469132661">
<div>
Is this correct syntax if I place it in my dataset within BIRT?
</div>
</blockquote>
No, the syntax is not correct, nor would I do it that way. In the data set I would have:
<pre class="_prettyXprint">
where year(date_field) = ? and month(date_field) = ?</pre>
and then I would bind the report parameters to the SQL parameters. This is the optimal way to pass parameters to reports as it avoids SQL injection. See picture (as I do not have the same version as you there might be some differences).