SUM Conundrum OR Bug?

customaware

Here is a curly one... Or maybe I am just tired...

I have a report, to which I pass an instance of a Non Persistent BO

In the report, I have a Sub Report that prints a heap of records that are the result of the following Query...

FIND EmployeeSalaryPlanPeriod WHERE EmployeeSalaryPlanPeriod.ob_EmployeeSalaryPlan.ob_Employee.ps_CurrentEntity=EntitySalaryReportParams.ps_SelectedEntity AND EntitySalaryReportParams.SelectedMonth BETWEEN EmployeeSalaryPlanPeriod.sc_SalaryPeriodStart AND EmployeeSalaryPlanPeriod.sc_SalaryPeriodFinish ORDER BY EmployeeSalaryPlanPeriod.sc_EmployeeName

This work perfectly.

Now I want to put a total at the bottom of these records.

I expected to be able to do this....

<<SUM EmployeeSalaryPlanPeriod.AllowanceDaily WHERE(EmployeeSalaryPlanPeriod.sc_EmployeeEntity=EntitySalaryReportParams.ps_SelectedEntity.EntityCode AND EntitySalaryReportParams.SelectedMonth BETWEEN EmployeeSalaryPlanPeriod.sc_SalaryPeriodStart AND EmployeeSalaryPlanPeriod.sc_SalaryPeriodFinish)@'#,##0'>>

But I get an error: Error filling report ../DocTemplates/customaware_38.33/DocTemplates/219/219/03392145954150827_RDDoc31491788547389648.rdd java.lang.ClassCastException java.lang.Boolean cannot be cast to java.lang.Number

Thinking maybe Aware does not like the BETWEEN, I changed it to this...

<<SUM EmployeeSalaryPlanPeriod.AllowanceDaily WHERE(EmployeeSalaryPlanPeriod.sc_EmployeeEntity=EntitySalaryReportParams.ps_SelectedEntity.EntityCode AND EmployeeSalaryPlanPeriod.sc_SalaryPeriodStart<=EntitySalaryReportParams.SelectedMonth AND EmployeeSalaryPlanPeriod.sc_SalaryPeriodFinish>=EntitySalaryReportParams.SelectedMonth)@'#,##0'>>

Still not go.

I have tried...both of the above without the number format at the end.

<<SUM EmployeeSalaryPlanPeriod.AllowanceDaily WHERE(EmployeeSalaryPlanPeriod.sc_EmployeeEntity=EntitySalaryReportParams.ps_SelectedEntity.EntityCode AND EmployeeSalaryPlanPeriod.sc_SalaryPeriodStart<=EntitySalaryReportParams.SelectedMonth AND EmployeeSalaryPlanPeriod.sc_SalaryPeriodFinish>=EntitySalaryReportParams.SelectedMonth)>>

So.. I tried trimming it down to test where the error is....

<<SUM EmployeeSalaryPlanPeriod.AllowanceDaily WHERE(EmployeeSalaryPlanPeriod.sc_EmployeeEntity=EntitySalaryReportParams.ps_SelectedEntity.EntityCode>>

Still No Go. Still the same error!

Am fresh out of ideas.

Anyone have any other suggestions or.... is this a bug?

BLOMASKY

Mark, this might not be much help but....

I use the standalone Jasper with Aware. When it brings the fields into the report, each field has a Java type (integer, decimal, boolean, etc.) Any yes/no field comes in as a boolean and while in the database, they are stored as 0 and 1, I can not do any comparison like field = 0 or field = 1. I have to either cast them as an integer or have a diff. field in aware that is a numeric field (and updated by the boolean)

However, I don't see where there would be any boolean in your SUM statement. That is confusing

Bruce

Jaymer

I’m not sure I’d say that’s a bug.
Usually a report writer SUMS a field that’s a column in the report. And a plain SUM would work in the report writer.
I think you’re going to have to have another field that has that value put in it based on your condition.
Then a regular SUM on that temporary field would give you your result.
You can do this in the full Jasper, but not in the embedded Jasper.
Mark Fredericks had to do this recently to do an aging report.
He had columns for 30 to 60, 60 to 90, 90 over.
He had to make fields in the BO and populate those fields before the report was run.
Then a SUM on those columns worked perfect.
I know that we have conditional SUMS in the bottom of the grid, but that may be because the kendo grid allows it.
Jasper SUM function may not allow a condition. And I’m not really sure I would expect it to.
Jaymer

customaware

Well.... I must have been tired...

Thanx for your comments and in particular Jaymer..... when you said..

Usually a report writer SUMS a field that’s a column in the report. And a plain SUM would work in the report writer.

That is exactly correct. Did not need a query for the SUMs at all.

Just a SUM of the Attribute in the Column Footer and all good.

Occam's Razor at it's best.