Bug 398084 - online update start date of import "last update" does not work for investment accounts
Summary: online update start date of import "last update" does not work for investment...
Status: RESOLVED FIXED
Alias: None
Product: kmymoney
Classification: Applications
Component: importer (show other bugs)
Version: git (master)
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-30 23:34 UTC by Jack
Modified: 2018-12-29 21:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 5.0.2


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jack 2018-08-30 23:34:27 UTC
For all money based accounts (checking, savings, credit card) if you map to an online account, under Edit account / Online settings / Import Details / Start date of import, you can select "Last update" and it will correctly remember.  However, for investment accounts, it does NOT remember the date of last update, and always uses Today minus 60 days.  If you look in the .kmy file, for accounts where this works, I see a keyvalue pair of lastImportedTransactionDate, but I do not see this for any investment account.

The recent commit 3e95b8c4ec4b640c83ce36d0623f1bdc8ca2d136 refers to this pair, but I cannot tell by context whether this applies to investment accounts.
Comment 1 Thomas Baumgart 2018-09-02 14:20:05 UTC
The said commit updates the lastImportedTransactionDate no matter if a statement balance record was found or not. Apparently, such a record is not provided for investment accounts which was the reason that the date contained in the DTEND tag was not written into the account structure as lastImportedTransactionDate. Can you verify that it is fixed and set the status appropriately?
Comment 2 Jack 2018-09-22 20:23:25 UTC
Even though the commit to address this won't work until the associated PR is accepted by libofx and they release a new version, should this be closed (noting the commit) since we know it works with the patches (one committed here, one pending for libofx) ?
Comment 3 Jack 2018-12-29 21:56:48 UTC
Sorry - I hadn't realized I needed to close this myself after confirming the mentioned commit did fix the problem.