Investment problem

Just loaded kmymoney 5.2.1 on Ubuntu; have been using an older version for years. Everything is ok except when adding an investment (buy shares) previously a box appeared asking if I wanted to add the investment. That does not happen in 5.2.1. I get a warning regarding not duplicating an investment in another account, but no indication of how that should be done. I am adding the transaction manually.

I agree that in the past, importing a transaction for a security would just add that security to the investment account without asking. That does seem to have changed, but I’m not certain if the change was intentional or an unintended side effect.

Either way, go to the Investment View, Equities Tab for that account. Right click and select New Investment. Type the name of the security in the Account Name field, click Next, and enter the symbol. When you tab or click into another field, it should use all the valued from the existing security. Once you accept all that, you should be able to do the import without problem.

1 Like

Thank you, that solved my problem. I have been using kmymoney for years and have always added an investment through the ‘buy shares’ route, and have consequently always gotten taken automatically to add inivestments.

I like the new tabbed interface btw.

I’m revisiting this because something does seem to have changed. In the past, if you purchased a security that did not yet exist in your data file, KMM added it. Now it simply ignores it. On and import (csv in this case) it just ignores the purchase completely. Does anyone know if this is an intentional change, or an unintended side effect of some other change? Even worse (or at least stranger) if I type the name of the new security and hit tab, it just selects some existing security silently, with no warning it is ignoring what I just typed.

I have had that happen too. I tried to select a new investment and it would not let me selecting another one instead. I thought that was some weirdness with my kmy file. What I ended up having to do is go back to KMM 5.1.3 and enter the transaction. It shows up ok in KMM 5.2.2 afterwards.