|
Notes |
|
|
|
It also does not work selecting EUR.
It seems that the problem are the Starting Date and Ending Date fields. If these fields are empty, the reports works but if any of these fields has a valid date, it does not work. |
|
|
|
(0026540)
|
|
hgbot
|
|
2010-04-21 13:08
|
|
|
|
|
|
Now the error message is displayed as There is no conversion rate defined from (EUR-€) to (USD-$) for date '07-08-2006', Client 'SmallBazaar' and Organization 'Main'.
Tested & working fine |
|
|
|
|
|
|
|
(0026682)
|
|
adrianromero
|
2010-04-26 15:25
(edited on: 2010-04-26 15:27) |
|
* Testing of the issue:
To test the issue just follow the steps to reproduce and execute the report with a currency different than EUR. Try to execute the report several times using different "Starting date" and "Ending date" values. The error message should always be similar to: There is no conversion rate defined from (EUR-€) to (USD-$) for date '07-08-2006', Client 'SmallBazaar' and Organization 'Main'.
* Explanation of the changeset that fixes the issue:
There has been modified the File HttpSecureAppServlet.java to get the causeException message instead of the JasperError Exception message. This is because the real message of the exception is in the causeException object.
It has been modified too the report template ReportPurchaseOrder.jrxml adding the function TO_DATE to the date parameters of the report to make the report work properly in Oracle and Postgresql.
* Other areas affected by the changeset:
The changes in the report template only affects to this report. And the changes in HttpSecureAppServlet.java affects to all jasper reports that throw an exception. The change is done the way if the causeException is an SQLException then use the SQLException message. That is the correct message that has to be translated and displayed to the user. In other case it will behave as before.
|
|
|
|
|
|
It has been set as resolved again because it needed another changeset for Oracle |
|
|
|
|
|
Retested in oracle context |
|
|
|
|
|