Home › Forums › implementation › Implementation discussion ›

1.7->1.7.1 Upgrade Statement printing error

Submitted by Ben_Charlton on Fri, 23/09/2016 - 13:13
in

I am doing a move for a client from Home -> Ec2 

I thought I would be nice and throw in an upgrade from 1.7 - 1.7.1

However is anyone aware of issues that might cause a some xpath strings in jrxml files to fail in particular in statements:

This is hte printexpression they used on the subreport...it works in 1.7 

new Boolean($F{shortName}.contains("customerAccountCharges") && !$F{shortName}.contains("customerAccountChargesCounter"))

Under 1.7.1

<exception>
<type>org.openvpms.report.ReportException</type>
<message>Failed to create report: Errors were encountered when compiling report expressions class file:
1. The type java.lang.CharSequence cannot be resolved. It is indirectly referenced from required .class files
value = (java.lang.Boolean)(new Boolean(((java.lang.String)field_shortName.getValue()).contains(&quot;customerAccountCharges&quot;) &amp;&amp; !((java.lang.String)field_shortName.getValue()).contains(&quot;customerAccountChargesCounter&quot;))); //$JR_EXPR_ID=28$
&lt;-------------------------------------------------------------------------------&gt;
1 errors
</message>
‹ OpenOffice Locking up System Ubuntu 16.04, MySql 5.7 and OVPMS 1.9 ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: 1.7->1.7.1 Upgrade Statement printing error

Submitted by Ben_Charlton on Fri, 23/09/2016 - 13:17.

Incidently when I removed this expression the next error was:

[ERROR,DialogErrorHandler,http-bio-8080-exec-3] Failed to generate report: Error evaluating expression :
        Source text : $P{dataSource}.getDataSource("items", new String[]{"target.patient.entity.name", "target.startTime"})

The reason given was no item node..

Caused by: net.sf.jasperreports.engine.JRException: No node found for field=items

Did we change something here in 1.7.1?

 

Regards
 
Ben 
OpenVPMS Installer and Helper 
Ph: +61423044823 
Email: info[at]charltonit.com[dot]au

Re: 1.7->1.7.1 Upgrade Statement printing error

Submitted by Ben_Charlton on Fri, 23/09/2016 - 15:05.

Invoice and Receipt printing works fine ...

Regards
 
Ben 
OpenVPMS Installer and Helper 
Ph: +61423044823 
Email: info[at]charltonit.com[dot]au

Re: 1.7->1.7.1 Upgrade Statement printing error

Submitted by Ben_Charlton on Fri, 23/09/2016 - 15:11.

Sorted its the Java 8 bug come back to bite me - I forgot 1.7 wasnt compatible

 

Regards
 
Ben 
OpenVPMS Installer and Helper 
Ph: +61423044823 
Email: info[at]charltonit.com[dot]au
Syndicate content