mc.bechara

But if i comment those 2 I'm getting the following error: java.lang.RuntimeException: groovy evaluation failed on string args[0].value and expression Integer(2015) and if I comment only the timestamp I get the following error: java.lang.RuntimeException: error getting schema

anyone help with this!

any ideas of the solution ?

I have an adhoc view with date filter in jasper 6.0. I imported that to another instance of jasper 6.1 and the date filter stopped affecting the adhoc view. Looking at the adhoc cache, I found out that in v.6.0 my query in jasper used to be and ("PO_DATE" > TIMESTAMP '2015-08-12 00:00:00') while in v.6.1 it's and ("PO_DATE" > '2015-08-12 00:00:00') that's why the error. My database is Oracle and I checked the semantics file in 6.1, mapping of date is correctly set to java.util.date What could be the problem?

anyone has a solution for this please? i'm not finding any in the forums.

oh by the way my database is oracle

@marianol I found out that in v.6.0 my query in jasper used to be and ("PO_DATE" > TIMESTAMP '2015-08-12 00:00:00') while in v.6.1 it's and ("PO_DATE" > '2015-08-12 00:00:00') that's why the error. But how to fix it? knowing that mapping of semantics is correct.

of course I clicked Apply and nothing happened. The domain was imported from v.6.0 and I have this in the log: xception calling JRDataSource.next() for query select * from ( select "PO_DATE", Sum("QUANTITY") as "Sum_QUANTITY", Sum("TOTAL_NET_PRICE_USD") as "Sum_TOTAL_NET_PRICE_USD"from "KARLOS"."VIEW_REPORT_PURCHASES"where "SCOPE_ID" = 'CB' and 1 = 1 and 1 = 1 and 1 = 1 and EXTRACT(YEAR FROM "PO_DATE") = 2015 and ("PO_DATE" > '2015-08-25 12:29:12')group by "PO_DATE"order by "PO_DATE" ) where ROWNUM <= 200001 at com.jaspersoft.commons.semantic.dsimpl.JRQueryDataSet$JRDataSetIterator.next(JRQueryDataSet.java:432)at com.jaspersoft.commons.datarator.CachedData.fetchData(CachedData.java:219)... 127 moreCaused by: net.sf.jasperreports.engine.JRException: Error executing SQL statement for: null.at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java:267)at com.jaspersoft.jasperserver.api.engine.jasperreports.util.JRTimezoneJdbcQueryExecuter.createDatasource(JRTimezoneJdbcQueryExecuter.java:168)at com.jaspersoft.commons.util.JSControlledJdbcQueryExecuter.run(JSControlledJdbcQueryExecuter.java:156)... 1 moreCaused by: java.sql.SQLDataException: ORA-01861: literal does not match format string

did the solution work? I have the same problem and I checked the semantic file, it is correct: <entry key="DATE" value="java.util.Date"/> <entry key="TIMESTAMP" value="java.sql.Timestamp"/> What else could be the problem?

I have an adhoc view with field myDate, when I add it to the filters and say myDate is After DAY-30 or any other time value, nothing is affected. There results don't get refreshed with this filter. However same report used to work with jaspersoft 6.0 Why isn't it working in version 6.1?

/default template is used. There's nothing out of normal in the adhoc view. Just normal columns, I have numbers, text and date columns.

I have Jaspersoft AWS version 6.0. I created an ad hoc view table with many columns grouped by one field. I saved the adhoc and created a report based on it. In the report not all columns visible in the adhoc view are visible in the report. Any ideas why? Is there a limit for the columns in the report?

this is what I got from the Log: ERROR errorPage_jsp,http-bio-80-exec-4776:580 - stack trace of exception that redirected to errorPage.jsporg.springframework.webflow.conversation.impl.LockTimeoutException: Unable to acquire conversation lock after 90 seconds

no errors just as if it goes timeout and loader keeps turning

I have the Jaspersoft AWS version installed and I have created many adhoc views and reports since long and everything was working perfect. Except few days again, when I click on any of my existing adhocs or reports, it keeps loading and never opens. My internet connection is good. My datasource is well connected to oracle. What is the problem?