[Kmymoney-devel] [kmymoney4] [Bug 320928] Warning of ": Unable to add transaction with valid postdate" during OFX import

[allan]

https://bugs.kde.org/show_bug.cgi?id=320928

--- Comment #22 from allan <agander93 at gmail.com> ---
On Fri, 21 Jun 2013 04:09:29 +0000
<mdaleknochenmus at gmail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=320928
> 
> --- Comment #21 from mdaleknochenmus at gmail.com ---
> OK, thanks.  Let's just drop it and I'll move on.

Just before that, there is just one point that puzzle me a bit.  The
file had been imported by libOFX, then the importer plugin without any
objection to the date.  It was only when the transaction was being
added to the statement that it was noticed.

I would be interested in taking a look at that, but would need your
file, or an extract from it.

You would need to disguise your account number and anything else of a
sensitive nature.  You'd need to take a backup first, of course, and
then if a mistake is made, there's no harm done.

I've also got hold of a routine to convert OFC to OFX, but again would
need a file to test.

Allan


> On Thu, Jun 20, 2013 at 9:32 PM, allan <agander93 at gmail.com> wrote:
> 
> > https://bugs.kde.org/show_bug.cgi?id=320928
> >
> > --- Comment #20 from allan <agander93 at gmail.com> ---
> > I suspect not.  If it were a new format, then it would be more
> > likely, but it appears to be obsolete, MS having dropped it I'm
> > favour of OFX nine years ago.
> > I did find reference to a converter, but that indicated that as it
> > didn't include a couple of needed. OFX fields, editing would be
> > needed, and you didn't sound too confident in your ability.
> > I think your best bet is one of the other formats.
> > Allan
> > On Jun 21, 2013 3:56 AM, <mdaleknochenmus at gmail.com> wrote:
> >
> > > https://bugs.kde.org/show_bug.cgi?id=320928
> > >
> > > --- Comment #19 from mdaleknochenmus at gmail.com ---
> > > Thanks for the update on the OFX v.s. OFC.  I agree that the bank
> > > is behind on
> > > their coding, however, your PlugIn window shows "ofc" as a valid
> > > file type, so
> > > I felt it fair to use that option!
> > >
> > > Also, I did check the (open) Date for the account on it's General
> > > tab,
> > and
> > > it
> > > was prior to the transactions I am attempting to import, so that
> > > is not
> > the
> > > issue.
> > >
> > > Assuming that I do want to import an OFC file type, will there be
> > > a fix
> > for
> > > this issue?  It isn't clear what the status is for my request.
> > > It isn't clear
> > > to me if this is going to be programmed or not.
> > >
> > > Thank you.

-- 
You are receiving this mail because:
You are the assignee for the bug.