Bug 341774 - OFX file import behavior
Summary: OFX file import behavior
Status: REPORTED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.6.6
Platform: Mint (Ubuntu based) Linux
: NOR wishlist
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-11 15:48 UTC by whelbig
Modified: 2018-05-18 04:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
OFX sample data set (2.49 KB, text/plain)
2014-12-11 15:50 UTC, whelbig
Details

Note You need to log in before you can comment on or make changes to this bug.
Description whelbig 2014-12-11 15:48:46 UTC
When importing an OFX file that contains multiple <BANKACCTFROM> </BANKACCTFROM> sections the Account Selection dialog is displayed for each occurrence. When the sections are identical the effective result of this behavior is to import the file one transaction at a time.

I suggest KMyMoney should recognize identical <BANKACCTFROM> sections and only present the Account Selection when it is different from the preceding one.

For reference see the user's mailing list thread in the archive at 
http://mail.kde.org/pipermail/kmymoney/2014-December/001992.html. Included in the discussion there is a small (~150 line) example data set.


Reproducible: Always
Comment 1 whelbig 2014-12-11 15:50:49 UTC
Created attachment 89921 [details]
OFX sample data set
Comment 2 Jack 2018-05-16 21:16:10 UTC
Does this still happen with a more recent version of KMM?  There have been changes to the import code - but I do not know if this behavior should have changed, as I do not have this issue with the OFX files that I import.
Comment 3 whelbig 2018-05-17 03:16:10 UTC
On 05/16/2018 05:16 PM, Jack wrote:
> https://bugs.kde.org/show_bug.cgi?id=341774
> 
> Jack <ostroffjh@users.sourceforge.net> changed:
> 
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |ostroffjh@users.sourceforge
>                     |                            |.net
> 
> --- Comment #2 from Jack <ostroffjh@users.sourceforge.net> ---
> Does this still happen with a more recent version of KMM?  There have been
> changes to the import code - but I do not know if this behavior should have
> changed, as I do not have this issue with the OFX files that I import.
> 

I do not know if this behavior still persists. The bank that produced 
the problematic file has merged with another institution and the .OFX 
file I now receive is nearly useless. There is a small sample file 
attached to the bug report that demonstrates the issue.

(To be clear the following is not a KMyMoney issue but rather a bank 
issue that illustrates some of the gross inadequates of this bank's .OFX 
implementation.

Almost every transaction downloaded must be edited to make it useful. 
There is no Memo field only the Name field is given.

I have/had two vehicle and a personal load open and paid automatically. 
The name that appears for all three is "Member Transfers" and the only 
way to distinguish which is which is by the transaction amount.

All Debit card purchases include the text ATM/Debit Card Purchase as the 
first 24 characters of a 30 character field leaving six characters for a 
unique name.

All checks written show Share Draft as the payee and do not even include 
the check number.

Probably more information than you wanted, but thank you for allowing me 
to vent.
Comment 4 Jack 2018-05-17 16:51:51 UTC
What version of KMM are you currently using.

Next, is the sample you attached in 2014 a sample of the old or new OFX?  If it's the old, please post a sample of the new style, just in case someone can suggest anything that would make the import work better for you.  I hate to just leave this open, if nobody currently has this problem.

Also - in most cases, KMM does use and remember the account number <ACCTID> to know into which account to import the data.  With the new OFX files, does it ask for the account every import, even though only once per import, or does it remember which account to use?
Comment 5 whelbig 2018-05-18 04:14:08 UTC
The KMM version I am using is 4.7.2 and the OS is Linux Mint 17.1.

Yes, both are older versions as is the majority of the software on my 
daily-use system. I generally only update for security updates or when 
new features I want/need are added. Stability and reliability of the 
system is my primary concern.

The sample I originally provided is the old OFX. Importing it into KMM 
demonstrates the issue. I am hesitant to call it a bug because a 
legitimate argument can be made that KMM does what it is designed to do 
and the problem is cause by a poorly created OFX file.

In my original report I stated the display of the Account Selection 
window was triggered by an occurrence of the <BANKACCTFROM> section in 
the OFX file. Reexamining the OFX it may be the trigger is actually the 
<ACCTID> field which is contained within the <BANKACCTFROM> section. In 
either case my work around was/is to pre-process the OFX and remove all 
duplicate occurrences of the <BANKACCTFROM> section. The end result is 
KMM only asks for account confirmation (via the Account Selection 
window) once at the beginning of the import rather than asking for each 
individual transaction.