Debtors workspace - error message
Hi
I am trying to get the debtors workspace up and running but I have encountered an error message. Debtors all list nicely and the report button produces a useful report.
The print button or the Generate statement button (under send all) however both result in the error message:
"Invalid configuration: Practice ******* ******** has no email contact for statements"
We intend to snail mail out statements and I assume this would be the default unless you purposely setup email
functionality. I tried assigning an email address to the practice but still get the error.
PS : Thanks Tony for explanation of reminder systems - practised on my cloned system and simple once understood what was meant to happen - once edited a few templates - should be sweet.
Cheers Geoff
Sorted part of the problem
Hi,
I had another go (?) at inserting an email location under practice and thats got me half way there. I can use the print button now for individual statement printing/previewing. It appears I need to specify an email address even if I dont wish to use email.
Send all however is throwing up "Invalid configuration: Template has no email text".
How do I get it to print the debtors statements on masse as its trying to email them?
Also Statement glitches:
1. Counter sale entries listed on a statement have Invalid property name:patient listed under them. Its obviously seeking a name when there isnt one - need it to ignore there being no patient for counter sales.
2. Also a few statements are throwing the error when try to print:
Failed to generate report: Error evaluating expression :
Source text : $P{dataSource}.getDataSource("items", new String[]{"target.patient.entity.name", "target.startTime"})
Ideas much appreciated will see if I can sort it meanwhile.
Cheers Geoff
Sorted part of the problem
Hi Geoff,
If a client has an email address with a 'billing' purpose selected for it, OpenVPMS will email the statement rather than printing it. One of your debtors must have an email with the billing purpose selected.
The message is telling you there is no text set for the email body in your statement template.
Hope that helps,
Matt Y.
Debtors Workspace
Thanks Matt,
But none of the debtors have an email address under contacts - so thats not causing the problem. If I have an
email address entered for the clinic I can print individual statements but 'Send All' wants to email rather than print.
If I have no email address for the clinic both 'print' and 'send all' want the clinic email entered.
Cheers Geoff
Debtors workspace - error
The statement generator requires that:
This is because it doesn't know ahead of time if any of the customers are receiving statements by email or not.
-Tim
Debtors workspace - error
Thanks Tim,
Simple if you know how.
To spell it out for anyone else. Even if you dont want to email statements you need to just type something in the 'Email body' field
and the Send All button works for printer output.
With regards to Counter sales causing 'Invalid property name:patient' to appear on the statement rather than having to use a marker
pen to cover the error message I have removed the $Fpatient.entity.name from the statement template until I can figure how to fix it.
It maybe that the girls are using counter sales in a way not intended but for charges from within the customer workspace it allows
sales to a client that you dont want attributed to a particular animal - a very useful feature. If they dont pay at the time :-( , it appears
on the statement and the lack of a patient name spawns the error.
The template is obviously looking for a patient name field for counter sales when one doesnt exist. Is there an entry in ireport that
avoids an error message if the field it seeks doesnt exist.
Much Thanks
Geoff
Debtors workspace - error
Hi Geoff,
I believe you need to modify the statement template to not try and detail counter sale invocies in the statement. I believe you can do this by modifying the "Print when expression" field on the Statement sub report to
new Boolean(!$F{printed}.booleanValue() && $F{shortName}.contains("customerAccountCharges") && !$F{shortName}.contains("customerAccountChargesCounter"))i.e only print when not already printed and is a charge transaction and not a counter sale transaction.
If want to still print details for Counter Sales transactions would need to do a bit more in the Statement Items template (the sub report) as this is grouped on Patient Name. Would need to put thinking cap on for this ...
Cheers
Tony
Error message debtors workspace
Hi,
Although we successfully got the debtors workspace and statement printing up and running we are still getting an error message when we try and print statements (or preview a statement) in the case of a few clients. The bulk of statements print without a problem.
The error message is : "Failed to generate report: Error evaluating expression :
Source text : $P{dataSource}.getDataSource("items", new String[]{"target.patient.entity.name", "target.startTime"})"
I would appreciate it if someone could decipher this and point me to what aspect of the clients record is throwing a spanner in the works. It has occurred for recent debtors as well.
Much Thanks
Geoff
Debtors workspace - error
Can you look in your openvpms-full.log and grab the whole stack trace for the above error message?
Error log
Hi,
Thanks for quick reply.
Just regenerated error and copied to attached text file.
Cheers Geoff
Error log
Hi Geoff,
I am pretty certain thsi is due to the customer having an unprinted Counter sale transaction and the setup of your current statement template. As counter sales don't have patients the current sub report that details an invoices lines when an invoice is not printed is trying to do the same for the counter sale.
To fix as per my post in May you need to change the subreport's "print when expression" value to
new Boolean(!$F{printed}.booleanValue() && $F{shortName}.contains("customerAccountCharges") && !$F{shortName}.contains("customerAccountChargesCounter"))Cheers
Tony
Error log
Thanks Tony,
I had modified it in May but hadnt had the opportunity to test it. Turned out I had modified the subreport tab changing
the 'use datasource expression' rather than the 'print when expression' under the common tab.
All sorted now
Much thanks Geoff