Advanced Reporting - OOTB Project Earned Value report returns error when start/end date parameters have values
Article ID: 246954
Updated On:
Products
Issue/Introduction
OOTB Project Earned Value report returns error when start/end date parameters have values
STEPS TO REPRODUCE:
1. Login to Advanced reporting and open PMO Report: Project Earned Value
2. Fill the Start Date/End Date input controls using the Calendar button and run the report in either immediate or scheduled mode
Expected Results: The report execution to returns the data without an error
Actual Results: The report displays Error Message: Error filling report
Error Message: 2022-07-29T06:21:54,758 ERROR AsyncJasperPrintAccessor,pool-7-thread-10:321 [] - Error during report execution
net.sf.jasperreports.engine.JRException: Error executing SQL statement for: CSK_PRJ_EarnedValue.
at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java:357) ~[jasperreports-6.14.0.jar:6.14.0-2ab0d8625be255bf609c78e1181801213e51db8f]
at com.jaspersoft.jasperserver.api.engine.jasperreports.util.JRTimezoneJdbcQueryExecuter.createDatasource(JRTimezoneJdbcQueryExecuter.java:181) ~[jasperserver-api-engine-impl-7.8.0.jar:?]
at com.jaspersoft.commons.util.JSControlledJdbcQueryExecuter.createDatasource(JSControlledJdbcQueryExecuter.java:115) ~[ji-datarator-7.8.0.jar:?]
at net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(JRFillDataset.java:1257) ~[jasperreports-6.14.0.jar:6.14.0-2ab0d8625be255bf609c78e1181801213e51db8f]
at net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(JRFillDataset.java:726) ~[jasperreports-6.14.0.jar:6.14.0-2ab0d8625be255bf609c78e1181801213e51db8f]
at net.sf.jasperreports.engine.fill.BaseReportFiller.setParameters(BaseReportFiller.java:457) ~[jasperreports-6.14.0.jar:6.14.0-2ab0d8625be255bf609c78e1181801213e51db8f]
at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:584) ~[jasperreports-6.14.0.jar:6.14.0-2ab0d8625be255bf609c78e1181801213e51db8f]
at net.sf.jasperreports.engine.fill.BaseFillHandle$ReportFill.run(BaseFillHandle.java:135) [jasperreports-6.14.0.jar:6.14.0-2ab0d8625be255bf609c78e1181801213e51db8f]
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$SynchronousExecutor.execute(EngineServiceImpl.java:959) [jasperserver-api-engine-impl-7.8.0.jar:?]
at net.sf.jasperreports.engine.fill.BaseFillHandle.startFill(BaseFillHandle.java:181) [jasperreports-6.14.0.jar:6.14.0-2ab0d8625be255bf609c78e1181801213e51db8f]
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$AsynchronousReportFiller.fillReport(EngineServiceImpl.java:910) [jasperserver-api-engine-impl-7.8.0.jar:?]
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.fillReport(EngineServiceImpl.java:1857) [jasperserver-api-engine-impl-7.8.0.jar:?]
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportFill.runWithDataSource(EngineServiceImpl.java:1162) [jasperserver-api-engine-impl-7.8.0.jar:?]
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportFill.runReport(EngineServiceImpl.java:1103) [jasperserver-api-engine-impl-7.8.0.jar:?]
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportRunnable.run(EngineServiceImpl.java:981) [jasperserver-api-engine-impl-7.8.0.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
Caused by: org.postgresql.util.PSQLException: ERROR: could not determine data type of parameter $5
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutor
Environment
Release : 16.0.1
Component : Clarity Jaspersoft 7.8
Resolution
Clarity Engineering team has fixed the OOTB Project Earned Value report and it should no longer return an error when the start/end date parameters have values. The issue required a code change and the fix will be included in the next release Clarity 16.1.0.
Feedback
