multiple display of the same transaction

[David Carlson]

On 4/3/2012 11:43 PM, Stuart McGraw wrote:
> [snip]
> To clarify, "one line" in this context means an entry
> (what I view as a transaction) in the a register tab, not
> a split line shown as part of a transaction viewed in
> Auto-split or transaction journal view.
>
> Since I argue that it is more useful (and very common)
> to view registers as showing transactions, I would expect
> "Delete" to delete the transaction it is executed in.
>
> I think if there's a bug[*1], it is the showing of a 
> transaction multiple times when it contains multiple 
> splits for the same account.
That only happens in 'child' accounts.
>> Before reporting it, though, be sure that you
>> have not accidentally turned off the delete warning confirmation.  Go to
>> Actions:Reset Warnings to check whether that is the case.
> Not sure why the delete confirmation choice would affect 
> anything.
>
If a user is in a 'child' account rather than a 'parent' account, he
might accidentally be trying to delete a single split from a multiple
split transaction.
> ----
> [*1] I wouldn't actually call it a bug, more an artifact
> of the implementation.
>
Going back to your original email:
"

When a transaction that has more than one split for the 
same account is viewed in that account's register, one 
sees the transaction displayed multiple times.

Three cases I've encountered when this may happen (I'm 
sure there are more):
* The recommended way of selling stock has one enter 
  the stock account in two splits in the same transaction.
* To change the basis cost of a stock, such as in a spinoff
  transaction, it is convenient to sell it and buy it back
  at a different price in two splits in one transaction.
* When consolidating multiple previous transactions into
  one: eg, a "receipts" account for incoming checks.
  When they are deposited, it is convenient to structure 
  the deposit transaction as a split, one for each of 
  the checks."


For the stock or commodity transactions, the split lines are there to
separate actions rather than stocks or commodities, the basis of the
account. This is a different can of worms that only investors would be
interested in.

Your third example is an aggregated deposit slip transaction. Wouldn't
such a transaction normally be viewed from the 'parent' bank account
rather than the 'child' Receipts account?

My example, the paycheck, would normally be viewed from the 'parent'
bank account rather than the 'child' taxes account(s).  Oops, in my case
there are deposits to more than one bank account as well as 401(k).

The multiple lines per transaction issue only arises when viewing a
transaction from a 'child' account, which is not the usual 'parent'
account that most of us would use.

This may be why no-one else has been bothered by that 'artifact'.

So my question to you is: When would a user be viewing a transaction
from the 'child' side?

David Carlson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xDC7C8BF3.asc
Type: application/pgp-keys
Size: 1729 bytes
Desc: not available
URL: <http://lists.gnucash.org/pipermail/gnucash-user/attachments/20120404/0c9da935/attachment.bin>