I did a csv import of two dividend transactions for “BLACKSTONE INC.” (BX). They were imported to “BLACKSTONE GROUP LP COM UNIT REPS” which is closed.
The ledger shows “Blackstone Inc.” as the Security, but that one is open. Showing transaction details shows the wrong security is actually referenced. Trying to edit the transaction fails because the security is closed.
Should importing investment transactions to a closed security be allowed?
Unfortunately, both security accounts refer to the same underlying equity (and thus use the same symbol (BX) which I suppose likely related to both issues. I know I can reopen the security account and fix the error, but what can/should be done to prevent future recurrences?
WRONG! Turns out this is related to my post in Investment problem - #3 by meljewett . If I reopen the closed security, even if I choose Blackstone, Inc in the dropdown, as soon as I move to a different field, it automatically reselects the wrong security. I thought I had found a workaround for this in the past, but certainly can’t think of it now.
OK, if I select the correct security using only the mouse, and not the keyboard, and then click into a different field (memo in this case) the correct security remains selected. Should it really matter whether you leave that field by keyboard or mouse?
I believe it is related - the same underlying cause. Perhaps KMM is finding the underlying security first, and then always choosing the first/oldest security account for that security. I have not looked at any of the actual code yet. It may be that having two security accounts referring to the same underlying security (at least using the same symbol) was never actually anticipated. Unfortunately, while it might be considered an incorrect/inappropriate configuration, stocks are well known to change their name on occasion but keep the symbol.
Jack, the problem is not related to the two securities using the same symbol. As was described in that linked thread, just mouse-clicking on the security in the drop down and tabbing out of the field caused the security to “magically” jump back to the previous in the list – even though the two have different symbols. Fun times! A
I have also experienced what Atheist describes. Seems the way to get around it is to enter transaction with the changed to wrong security, save it, then delete it, and then re-enter it. The second time, it takes the selected security.
A