Report Issues with Double --> Decimal transition

Documentation Configuration & Installation
1

Starting in 6.8.02, nearly all Double fields were converted to BigDecimal fields in the database.

This can cause some issues for databases using these fields in unusual ways, but primarily, this change can stop reports and labels from running properly.

Error evaluating expression:

When running a report with the incorrect field class type, you may encounter this error:

net.sf.jasperreports.engine.fill.JRExpressionEvalException: Error evaluating expression :

The most common problematic fields are minElevation and maxElevation in the Locality table in the Specify Schema.

Below are instructions to resolve this error in Specify:

  1. Open the report that is reporting an error in SpiReport and expand the fields list.
    In this instance, I am selecting Max_Elevation.

Select troublesome field in the field list
Select troublesome field in the field list3824×2474 1.09 MB

  1. Change the Field Class Type to java.math.BigDecimal

Change field class type
Change field class type896×568 76.4 KB

  1. Save your report or label. Refresh the reports in Specify 6 and you should no longer have any issue!

You can repeat this process for each problem field and the report will run correctly as it did before the 6.8.02 schema update!