GnuCash
Contact   Instructions
Bug 642824 - Different actions like QIF import, other imports and closing book allow to assign transactions to placeholder accounts
Summary: Different actions like QIF import, other imports and closing book allow to as...
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Engine (show other bugs)
Version: git-master
Hardware: Other All
: Normal normal
Target Milestone: ---
Assignee: core
QA Contact: Christian Stimming
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-20 12:54 EST by Frank H. Ellenberger
Modified: 2019-05-13 05:18 EDT (History)
6 users (show)

See Also:


Attachments

Description Frank H. Ellenberger 2011-02-20 12:54:07 EST
The QIF import module allows assigning of placeholder accounts. This is not such a bad idea, as it seems on the first view.

But later you open that account to move the transactions to the right subaccounts and get the warning about the write protected account. Then you can remove the placeholder flag, edit the transactions and add the flag again.

I believe, at least a warning should pop up in the import druid, if the user assigns a placeholder account as he usually selected the wrong account.

To improve the GUI, a dimming of placeholder accounts would be nice - or an option to filter them away.
Comment 1 Christian Stimming 2011-02-21 03:03:27 EST
I think the same error exists in all the other imports as well. (Can't find the duplicate, though.)
Comment 2 Frank H. Ellenberger 2011-03-04 18:33:04 EST
On gnucash-de we got the message, also "book closing" is affected:
http://lists.gnucash.org/pipermail/gnucash-de/2011-January/007755.html

So I move this report to engine.
Comment 3 Bob 2019-05-13 05:18:45 EDT
Changed the account selection in the account tree views to exclude place holder accounts from selection with a warning to that effect which also controls the OK button. The OFX / CSV importers already had a warning dialogue but this was changed to warning message as above to be less disruptive.

This will be in version 3.6

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