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

aga agander93 at gmail.com
Wed Jun 19 22:11:04 UTC 2013


On Wed, 19 Jun 2013 17:27:37 +0000
Jack <ostroffjh at users.sourceforge.net> wrote:

> https://bugs.kde.org/show_bug.cgi?id=320928
> 
> --- Comment #13 from Jack <ostroffjh at users.sourceforge.net> ---
> > I read the ID as '', ie. empty, which probably because the error
> > has already been discovered by KMM - that is , the date problem. 
> 
> I can't imagine KMM would omit the ID of the transaction, since that
> would be the only way to find the error.  We also still don't know
> whether the problem is with the date format or with the actual date.

It hasn't yet got to the point of adding an ID as the checks are not
yet complete.

Near the beginning of MyMoneySeqAccessMgr::addTransaction(MyMoneyTransaction&
transaction, const bool skipAccountUpdate) {
  // perform some checks to see that the transaction stuff is OK. For
  // now we assume that
  // * no ids are assigned
  // * the date valid (must not be empty)
  // * the referenced accounts in the splits exist

  // first perform all the checks
  if (!transaction.id().isEmpty())
    throw new MYMONEYEXCEPTION("transaction already contains an id");
  if (!transaction.postDate().isValid())
    throw new MYMONEYEXCEPTION("invalid post date");

The failure occurs on the date check, so the ID has been checked and
found to be empty, as expected.  Had the date been correct, the ID
would have been added later.

Allan 



More information about the KMyMoney-devel mailing list