GnuCash
Contact   Instructions
Bug 796758 - Improve error messages, why one can not remove a tax table
Summary: Improve error messages, why one can not remove a tax table
Status: NEW
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Business (show other bugs)
Version: 3.2
Hardware: PC Linux
: Normal normal
Target Milestone: ---
Assignee: core
QA Contact: core
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-14 01:09 EDT by Frank H. Ellenberger
Modified: 2018-08-14 15:29 EDT (History)
4 users (show)

See Also:


Attachments

Description Frank H. Ellenberger 2018-07-14 01:09:58 EDT
I am in the example file from Jeremy D's answer to https://lists.gnucash.org/pipermail/gnucash-user/2018-July/078170.html, which is until now not on the list.

Because I can not rename the tax table (Bug 580253 - Ability to rename tax tables) I try to delete it. The table has one entry only and there are no transactions in the file visible. 

If I try to delete the entry, I get 
"You cannot remove the last entry from the tax table. Try deleting the tax "
"table if you want to do that."

If I try to delete the table, I get
"Tax table \"%s\" is in use. You cannot delete it.".

What can I do now?
Comment 1 Frank H. Ellenberger 2018-07-14 02:27:50 EDT
Looking with a text editor in the file, I found an invoice using it.

So I would suggest to improve the error messages:

I would expect the error message on the entry, which is in use.
"You cannot remove the entry from the tax table. It is in use by %u probably unposted invoices, %u clients and %u vendors." and buttons to list that invoices, clients and vendors
or in our case "The last entry of tax table \"%s\" is in use by %u ...
Comment 2 Adrien 2018-08-14 15:29:58 EDT
Thank you!

I have some tax table entries I can't delete and can't track down which documents use them so I can switch them to the more recent 'correct' versions I've since created. (I couldn't change them either, as they were 'in use' so I had to create new entries) This revised message would be much more helpful.

Note You need to log in before you can comment on or make changes to this bug.