[Kmymoney-devel] [kmymoney4] [Bug 338076] Download OXF of investment transactions all set to 'category' "investment transaction".
agander93 at gmail.com
Thu Aug 7 11:33:57 UTC 2014
--- Comment #8 from allan <agander93 at gmail.com> ---
> > > ...I suspect the bit of code I am talking about is shared by both OFX
> > > QIF.
> > No, that's not the case. They are handled by quite different classes,
> > /kmymoney/kmymoney/converter/mymoneyqifreader.cpp and
> > /kmymoney/kmymoney/plugins/ofximport/ofximporterplugin.cpp. The code I
> > fixed was in the former.
> But don't these bits of code just reformat the transaction and send it up
> the line to the code that actually puts it in the account?
They handle things differently. For instance, the code of
ofximporterplugin.cpp does not contain any mention of "brokerage". When I last
looked at this, I came to the conclusion that in OFX parlance, brokerage refers
to the broker supplying the file, and it has no knowledge of KMM innards, such
as default brokerage accounts.
> In any case, I seem to be getting the same result from my QIF import as the
> OFX import is generating. Here is a scrap of QIF that shows the same thing:
> NFidelity 58
> D(800) 544-6666
> D8/31' 6
> YFDRXX FIDELITY CASH RESERVES
> MDIVIDEND RECEIVED
When I first looked at this, it seemed more or less identical to your previous
QIF snippet, so I was quite surprised when I imported it and it gave different
results. That is, the imported transaction was missing the brokerage account.
I didn't think it relevant, but the "!Account" entry was the cause. When I
removed it, I was prompted to supply the account for the import. I then
realised that previously your import had worked because I had selected an
account tha had an existing brokerage account. The "!Account" entry was
creating a new account, which would not have a brokerage account. So, I had
misled myself, and you, into thinking your problem had been fixed. It has not.
The reason is that the existing code will only create a new brokerage account
if the transaction either has an "X" suffix to the action code, or a transfer
account name in  .
This area of code is long eastablished, and it seems, if I understand you
correctly, the problem is the result of recent Quicken versions moving the
goalposts away from their long-established "standard".
@Thomas. Thomas, what is your view on how this issue should be resolved? Do we
commit to following Quicken, where-ever it chooses to go?
> > I don't have any OFX accounts, but if you are able to provide an OFX file
> > that demonstrates this behavior, I will try to look at it.
To be able to investigate the OFX issue, I will need a file that demonstrates
the problem. Comparing with QIF is useless, I'm afraid. However, from what I
said above, OFX has no awareness of KMM's file structure.
You are receiving this mail because:
You are the assignee for the bug.
More information about the KMyMoney-devel