SQL-Ledger Homepage

SQL-Ledger User Forum

Forum index page

Log in | Register

Back to index page
Thread view  Board view
DavidJ(R)

25.04.2016, 20:07
 

Bug in Add Transaction/s [SOLVED] (General)

Hi Support
We're finding a small but irritating issue.
We're using 3.0.5, so IF this is already fixed in later version, then I'm sorry for raising old problem.
I did search the recent changelog for any mention of this issue, but none found.
It goes like this.
AP/Purchases, Add transaction, from the dropbox, select a supplier/vendor that does NOT charge tax.
The tax boxes disappear from the input window as expected.
With or without making any entries or posting, use the dropbox and change the supplier/vendor to another supplier/vendor that DOES charge tax.
The tax box reappears BUT the default is UNTICKED.
This is not quite the desired outcome. IMHO this should be ticked.
Grateful for any tips or clues for how to fix.

PS. Of course, Add transaction works as expected when selected from SQL-L menu, and the supplier/vendor that charges tax is selected first.

Edit #1. Perhaps this issue emerges only for Supplier/s who have been ticked as "Tax inclusive". Further testing will confirm.

DavidJ(R)

27.04.2016, 08:14

@ DavidJ
 

Bug in Add Transaction/s

I was hoping this wrinkle might disappear in SQL-L version 3.2.
Unfortunately, testing confirms this problem persists in latest version.

DavidJ(R)

08.05.2016, 07:47

@ DavidJ
 

Bug in Add Transaction/s

Here's why this issue looks like a bug, and simple steps to reproduce.

User enters a purchase transaction against a Vendor that does NOT charge tax.
Update and post as usual.

Start another AP, Add Transaction.
The Add Transaction screen defaults to the last Vendor used. (Remember, the last one didn't charge tax)
User immediately selects a different Vendor that does charge tax AND has Tax inclusive checked, BUT the tax box remains unchecked.
This is confusing, and probably sub-optimal.
It also encourages error/s.

Dieter, hopefully you're not busy fighting wildfires, and will have time to help with comment sometime. TIA's

Dieter Simader(R)

09.05.2016, 15:29

@ DavidJ
 

Bug in Add Transaction/s

Here's why this issue looks like a bug, and simple steps to reproduce.

User enters a purchase transaction against a Vendor that does NOT charge
tax.
Update and post as usual.

Start another AP, Add Transaction.
The Add Transaction screen defaults to the last Vendor used. (Remember,
the last one didn't charge tax)
User immediately selects a different Vendor that does charge tax AND has
Tax inclusive checked, BUT the tax box remains unchecked.
This is confusing, and probably sub-optimal.
It also encourages error/s.

Dieter, hopefully you're not busy fighting wildfires, and will have time to
help with comment sometime. TIA's

edit aa.pl "v3.2", after line 1237 "foreach $item (@taxaccounts) {"

add

$form->{"select$form->{ARAP}_tax_$item"} = qq|$item--$form->{"${item}_description"}|;
$form->{"calctax_$item"} = 1 if $form->{calctax};

DavidJ(R)

10.05.2016, 18:55

@ Dieter Simader
 

Bug in Add Transaction/s

edit aa.pl "v3.2", after line 1237 "foreach $item (@taxaccounts) {"

add

$form->{"select$form->{ARAP}_tax_$item"} = qq|$item--$form-> "${item}_description"}|;
$form->{"calctax_$item"} = 1 if $form->{calctax};

Dieter, very many thanks for this tiny patch.
Note to self and others. Remember to buy copy of latest SQL-Ledger manual and continue to support this great project.

Back to index page
Thread view  Board view
965 Postings in 318 Threads, 323 registered users, 169 users online (0 registered, 169 guests)
SQL-Ledger User Forum | Admin contact
RSS-Feed
powered by my little forum