Home
Designing Analytics Reports
Date Parameter confuses the year for MM/DD/YY input to mean 19YY and not 20YY
Migrateduser
<p>I developed a BIRT report using Eclipse (Version: 3.7.1) which uses a single date parameter to query for records with a specific date. I used the function MXReportSqlFormat.getStartDayTimestampFunction in the report SQL statement to evaluate the date entered for the parameter. This is because the dates I'm querying for are just the date and not the date & time (time set to all zeros).</p>
<p> </p>
<p>What I noticed is that sometimes the date is not read correctly. For example, when I enter 1/1/50, the report uses the date "1/1/1950" in the report SQL statement. It is only when I enter the date as "1/1/2050" that it correctly uses the year I intended to use when I typed in "1/1/50." Is this a known issue within BIRT or Eclipse?</p>
<p> </p>
<p>Also, the BIRT report was created to be used within Maximo. In Maximo, the parameter is setup to use the <em>datelookup </em>to have a calendar picker to accurately select the date. Once the user selects 1/1/2015 (or 1/1/1950) from the calendar, it displays "1/1/50" and it works only when the date is "1/1/1950" for the record. But in Maximo, even if I type in "1/1/2050," it still uses "1/1/1950" so I cannot query for records with the date "1/1/2050."</p>
<p> </p>
<p>What can I do to resolve this? This is a big issue since all dates that will be queried for are future dates.</p>
<p> </p>
<p>Thanks in advance for your help.</p>
Find more posts tagged with
Comments
There are no comments yet