Version: 0.9 (using KDE 4.2.0) OS: Linux Installed from: Ubuntu Packages Hi Kmymoney developers, I imported my structure from gnucash and now I found that some account types are not set correctly. (e.g. Cash instead of Bank account) Unfortunately it is not possible to change the account type, so, if it is not too much effort to implement, I would like this feature. thanks, Stefan :)
I encountered the same problem on Ubuntu 9.04, using Version 0.9.2. I can create new accounts and changed their account types, but not the old imported ones from Gnucash.
There has been a long outstanding feature request for this here: https://sourceforge.net/tracker/index.php?func=detail&aid=1359963&group_id=4708&atid=354708 It shouldn't matter whether the account was imported from GnuCash or not; the fact that it was imported is not saved with the account.
Moving this wish to kmymoney4.
I don't know if this was intentionally addressed, but it changing account type IS currently permitted, but only within the same basic type of account. Savings, checking, and cash for example. Credit card accounts cannot be changed, and I don't know if this limitation is reasonable or not. However, I think the more appropriate approach would be to confirm account types with the user at the time of import.
The types that one can change account from/to are definitely too limited, and I discussed this previously, possibly even created another (duplicate) issue about it, but can't find it now.
Is this still a problem? If Dawid's comment is still relevant, then I'll change the subject to be more appropriate. However, I would ask what pairs of account types currently do not allow changing between, but should.
It is probably easier to explain what can be changed. You can change freely between 'Cash', 'Savings' and 'Checkings'. All others are fixed. We can certainly add more powers here but this might cause other trouble down the line. The code is located (currently) at https://invent.kde.org/office/kmymoney/-/blob/master/kmymoney/dialogs/knewaccountdlg.cpp#L273
So should this be closed as WONTFIX? This has been discussed on the mailing list more than once, and the workaround is to create a new account of the correct type, and then move all the transactions. Not a trivial task, but it works.
I'd say it's a valid issue and should eventually get fixed. The logic deciding whether or not an account type can be changed and to which type should be moved to the Account Type model and defined for each type individually. Right now there's a dedicated piece of code that handles that, which doesn't consider all transitions.
I'm changing back to REPORTED (it is already a wishlist) and it can be closed if someone finds another bug for the same requqest.