[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 Ralf Habacker changed: What|Removed |Added Component|bugtracker |general --- Comment #10 from Ralf Habacker --- Moved to 'general' component -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 Michael Carpino changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #9 from Michael Carpino --- *** This bug has been marked as a duplicate of bug 392603 *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #8 from Michael Carpino --- I've defined the problem better with a different bug and marked this as a duplicate. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #7 from Michael Carpino --- Ok I'll take your advice and unmap the brokerage/checking account and update the accounts 1 account at a time. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #6 from Jack --- I strongly suspect, but have no proof, that you will end up with more problems if you map the brokerage account. (In fact, I believe that KMM should warn you if yo do try to map a brokerage account, but it seem to only know that if you accept the default name for it, which is "(Brokerage)" appended to the name of the investment account. I don't know if there is a bug filed already for KMM asking where to put the "checking" transactions. If you only update one account at a time, you can know which brokerage account to specify, so until this is sorted, I would just advise against updating all at once. Also,, you should not be able to map more than one KMM account to the same online account, or else it wouldn't know which account to use. (That is true in general, although Investment accounts are of course different...) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #5 from Michael Carpino --- With 5.0 the only way to kinda getting it to work is to Map both accounts (Brokerage and Investment) and the transactions are dumped into the checking account. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #4 from Michael Carpino --- Yes, I dualboot and went to my windows 10 KMM 4.8.1.1 and the transactions are going into the investment account as you stated. With 5.0 the issue is it asks everytime what checking account you want to use. And there is no description on what account its referring to so you're clueless when you have more than 2 on what to do. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #3 from Jack --- So we need to fix the docs somehow, to make it clear how to handle this situation. You should ONLY map the investment account, and NOT the brokerage (checking) account. When you download, any cash transactions are correctly put in the associated brokerage account. (At least they used to be. Now, you may need to specify the brokerage account when KMM asks what checking account to use when you do the first update.) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #2 from Michael Carpino --- I tried a few different things which is appears to cause a linking issue or lack there of. First I deleted the passwords in KDEWallet to make sure the passwords where being set there correctly. Then I unmapped the investment accounts. With my first brokerage account(TD Ameritrade), I went the checking account and mapped the checking account by selecting account > map account > ofximporter > TD Ameritrade. After finalizing I verified that I can update and it works. But if I go to the Investment Ledger for this account it is still showing Unmapped. I can go through all the steps and map it but there is some type of linkage problem I didn't have to do this in earlier versions. With my other brokerage account (Fidelity NetBenefits) I went through the same steps above except I started by mapping the Investment ledger. Then I went to the (brokerage) checking account and it shows it isn't mapped. When I look in KDEWallet the paswords are stored there correctly. I have other accounts that are not "Brokerage" type and mapping is working just fine. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391454] passwords not integrating (storing) with KMM 5.0 and KDEWallet properly
https://bugs.kde.org/show_bug.cgi?id=391454 --- Comment #1 from Jack --- I think the issue of KMM asking for the user to identify the checking account is a separate bug (I do not think yet reported, but I think I mentioned it on the mailing list) where it should automatically choose the Brokerage account for the Investment account being processed. I also think I reported to the mailing list the issue that accounts which were mapped in 4.8 did not show as mapped in 5.0. However, that issue was fixed in 5.0, even though it seems at least partly similar here. Also, please clarify which OFX you are using, and your process to map the account. From memory, you have to specify the ID and password when you map the account, and it should save them then. If you have to specify them again when actually updating the account the first time, then there might be some problem with password storage. I know I have not had any problem udpating accounts (OFX, not aqbanking) with 5.0. -- You are receiving this mail because: You are watching all bug changes.
