Summary: | OFX import leaves brokerage account field blank for nested accounts | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | Jeff Carlson <jeffmcarlson> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | me, ostroffjh |
Priority: | NOR | ||
Version: | 4.7.2 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/kmymoney/fc3926479ed186ae2166e6701d267eb0b3f09a07 | Version Fixed In: | 5.1.0 |
Sentry Crash Report: |
Description
Jeff Carlson
2015-07-19 01:40:21 UTC
I believe that is has nothing to do with the brokerage account being nested. If I remember from dealing with a similar issue, KMM will only use the brokerage account automatically if it has exactly the default name, which is the name of the investment account followed by " (Brokerage)". Bug 329701 is a wishlist for exactly this issue. Can you confirm if this is still the case? I know the brokerage account field does start out blank for imported investment transactions, but once you edit the transaction, they are usually filled in automatically. Git commit fc3926479ed186ae2166e6701d267eb0b3f09a07 by Thomas Baumgart. Committed on 09/05/2020 at 04:55. Pushed by tbaumgart into branch '5.0'. Detect brokerage account based on partial name The detection of a brokerage account connected to an investment account did not work if the brokerage account was not a top-level account (sub-account of Asset or Liability). This change allows to locate the brokerage account based on its name in any hierarchical level of the account structure. FIXED-IN: 5.0.9 M +3 -0 kmymoney/converter/mymoneystatementreader.cpp https://commits.kde.org/kmymoney/fc3926479ed186ae2166e6701d267eb0b3f09a07 |