[kmymoney] [Bug 390681] OFX import and unrecognized <FITID> tag

[Brendan Coupe]

I wanted to follow up on the change that added the option to use the
KMM Hash to generate FITIDs globally.

At first this worked for the Citi credit card and then it stopped
working toward the end of the statement period. I decided not to judge
it until it was used for an entire statement period and my patience
paid off. The first full month worked perfectly. I have checked the
Citi OFX file and the FITID number is still not following the OXF
standard and is simply the date followed by a sequential number
starting with the first transaction in the file.

Since this is a global setting I had to shorten the OFX download time
frame for the rest of my accounts. After enough time passed most of my
accounts are working fine with the KMM hash method and I have extended
the ofx download time frame for all of them.

Is this setting going to be added to the KMM settings? Is there any
chance it will be account based rather than global? The global setting
does have the temporary side effect of not matching any previously
downloaded transactions that are downloaded again.

----
Brendan Coupe

On Sun, Apr 21, 2019 at 1:35 PM <bugzilla_noreply at kde.org> wrote:
>
> https://bugs.kde.org/show_bug.cgi?id=390681
>
> --- Comment #11 from Brendan at CoupeWare.com ---
> I tested this and it works. This is not ideal as a global setting
> since I have to decide if I want to fix the one account that does not
> handle the FITID numbers correctly or deal with every other account
> that has previous imported transactions. First guess is that will
> require me to go throut hundreds of new duplicates and delete the ones
> that are already reconciled / cleared.
>
> Is there any chance that this will end up being an account based
> setting or is global the only way to do this?
>
> ----
> Brendan Coupe
>
> On Fri, Apr 19, 2019 at 2:11 AM Thomas Baumgart
> <bugzilla_noreply at kde.org> wrote:
> >
> > https://bugs.kde.org/show_bug.cgi?id=390681
> >
> > --- Comment #10 from Thomas Baumgart <thb at net-bembel.de> ---
> > Git commit 9fca9e3661ce2d03e472ab1d520b59493ec110cb by Thomas Baumgart.
> > Committed on 19/04/2019 at 08:10.
> > Pushed by tbaumgart into branch '5.0'.
> >
> > Provide internal OFX id generation also for WebConnect
> >
> > The change provided in commit 65e3837697c93786 is not available when
> > importing an OFX statement file via WebConnect. For this case, a new
> > option has been added (no UI yet) to allow selection of the default for
> > the unique transaction id to be either the OFX FITID field or our
> > internal hash. The default is to use OFX FITID, so no change in prior
> > behavior. This default settings will also be used to preset the combo
> > box in the file selection dialog for OFX import and the account setting
> > for mapped accounts.
> >
> > If users set this option, they need to know that some duplicate
> > transactions may appear since the method to detect them changed. One way
> > to deal with that is to remove both transactions and redo the import.
> >
> > To set the method to the internal hash create a file named
> >
> >   ~/.config/kmymoney/ofximporterrc
> >
> > with the following content:
> >
> >   [General]
> >   useOwnFITID=true
> >
> > Future versions of KMyMoney will provide a UI to change this setting.
> >
> > M  +36   -11   kmymoney/plugins/ofx/import/ofximporter.cpp
> >
> > https://commits.kde.org/kmymoney/9fca9e3661ce2d03e472ab1d520b59493ec110cb
> >
> > --
> > You are receiving this mail because:
> > You are the assignee for the bug.
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.