Hello,
Can anyone figure out what subroutine update in bin/am.pl is meant to do?
This subroutine is triggered by button update in form generated from
template UI/am-taxes.html.
After clicking the button different times, depending on the initial
number of tax-accounts displayed,
you get a form where each initial line is followed by an empty line.
When clicking Save button, one gets:
ERROR: duplicate key value violates unique constraint "tax_pkey"
DETAIL: Key (chart_id, validto)=(53, infinity) already exists.
CONTEXT: SQL statement "INSERT INTO tax(chart_id, validto, rate,
taxnumber, pass, taxmodule_id)
VALUES (in_chart_id, in_validto, in_rate, in_taxnumber, in_pass,
in_taxmodule_id)"
PL/pgSQL function "account__save_tax" line 14 at SQL statement
So, after the actual commit-freeze is lifted, i would disable that
button, so that ons does not get frustrated by these errors.
+PROCESS button element_data={name => 'action', value => 'update',
text => text('Update'),disabled=>'true'};
PROCESS button element_data={name => 'action', value => 'save_taxes',
text => text('Save')} ?>
Best Wishes,
Herman
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Ledger-smb-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
