I mapped the old account to the new Citibank account and when i downloaded the past 6 months nothing matched. I manually matched everything and imported again and - again, nothing matched.
Any idea what I'm doing wrong? Glad I made a backup:-) *----Brendan* On Sun, Jul 17, 2016 at 7:26 PM, Brendan Coupe <bren...@coupeware.com> wrote: > Thanks for the help. I know that my OFX downloads failed 2 weeks ago when > i gave up and switched to the Fedora version for the first time in many > years. > > I modified my script to get the 4.8 branch. Here is the new git clone > command for anyone else wondering how to get the source. > > git clone git://anongit.kde.org/kmymoney --branch 4.8 > > This way I can get the bug fixes easily. > > I will wait for a while until KF5 settles down. > > I'm going to take your advice and map the old account to the new Citibank > Visa card. > > > > *----Brendan* > > On Sun, Jul 17, 2016 at 7:11 PM, Jack <ostrof...@users.sourceforge.net> > wrote: > >> [please don't top post] >> >> On 2016.07.17 19:13, Brendan Coupe wrote: >> >>> Is the OFX import relatively new to KF5? I submitted a question (see KF5 >>> - >>> GPG Encryption Problem) here a 2 weeks ago and Christian said it was not >>> working. My accounts are all mapped so it was not a mapping issue. >>> >>> I'll probably stick with 4.8 until KF5 is more stable. Are any changes >>> being made to 4.8 or is it done? I downloaded the source and compiled it >>> and imported my transactions for the Citibank Visa and it did the same >>> thing. If there will be no more bug fixes in 4.8 I'll stick with it until >>> KF5 is ready. >>> >>> >>> >>> *----Brendan* >>> >>> On Sun, Jul 17, 2016 at 3:53 PM, Jack <ostrof...@users.sourceforge.net> >>> wrote: >>> >>> > On 2016.07.17 18:39, Brendan Coupe wrote: >>> > >>> >> Nothing shows up on the command line that explains what is happening. >>> >> >>> >> It's a new bank and a new credit card so I'd prefer to leave it as a >>> new >>> >> account in KMM. I guess I could just treat it as "Costco Credit Card". >>> >> I've >>> >> thought about this with my other credit card that seems to be replaced >>> >> every 8 to 12 months for the past several years. The move to a new >>> account >>> >> is always painful. >>> >> >>> >> Since it's impossible to get the banks to follow the standard (don't >>> get >>> >> me >>> >> started on Charles Schwab) it seems to me that KMM should be doing 2 >>> >> things. It should discard all transactions prior to the starting date >>> that >>> >> it requests from the bank and it should discard all transactions >>> prior to >>> >> the opening date of the account. The download may still take a while >>> since >>> >> I'm getting everything but KMM can toss most of it out. >>> >> >>> >> I normally run from that latest source. I have 2 scripts that make it >>> very >>> >> easy to download, compile and install the very latest. I had to stop >>> using >>> >> them when KMM switched to the KF5 version since it does not handle OFX >>> >> files yet. >>> >> >>> >> Can I change the path in my script to get 4.8? It's currently git:// >>> >> anongit.kde.org/kmymoney. >>> >> >>> >> Thanks. >>> >> >>> >> >>> >> >>> >> *----Brendan* >>> >> >>> >> On Sun, Jul 17, 2016 at 2:45 PM, <jeffjl....@outlook.com> wrote: >>> >> >>> >> > > On 2016.07.17 15:48, Brendan Coupe wrote: >>> >> > > > Apparently Citibank is ingnoring the date range so it downloads >>> >> > > > everything it has which dates back over 6 months from when the >>> card >>> >> > > > was activated. >>> >> > >>> >> > I have this same problem with my Citi card. Sometimes it actually >>> uses >>> >> > the dates in the OFX request, but most of the time it returns every >>> >> single >>> >> > transaction for the last (I think) 2 years. (I've had the card for >>> >> longer >>> >> > than 2 years.) I tried modifying the OFX request and could not find >>> the >>> >> > magic words to make it work properly. >>> >> > >>> >> > In my case KMM would take about 2 or 3 minutes importing and trying >>> to >>> >> > match all those transactions, and as I recall, I would usually have >>> to >>> >> > manually fix/delete and/or re-accept the payment transfers. >>> >> > >>> >> > This won't help you, but I got tired of it and modified my copy of >>> the >>> >> > KMM statement importer to ignore transactions prior to the "Start >>> date >>> >> of >>> >> > import" in the account's online settings. >>> >> > >>> >> > Jeff >>> >> >>> > >>> > git includes both versions. It's just that master is now the KF5 >>> version, >>> > and 4.8 is in it's own branch. If you do "git branch -a" you will see >>> > which branch you need to checkout. Note that we have NOT yet >>> "switched" to >>> > Frameworks - the official current release is 4.8, but all developer >>> effort >>> > is going to complete the switch. Progress is certainly being made, but >>> > there is no official timeline. >>> > >>> > Also note, that OFX downloads do work in the frameworks version. (I >>> have >>> > tested with my bank, BOA credit card, and Merrill Lynch investment >>> > accounts.) However, you cannot map an online account yet. >>> > >>> > For your other suggestions, it is probably best to put them in new >>> > wishlist items on bugs.kde.org. I would probably word both as >>> requests >>> > for all imports, not just OFX, although I suppose honoring the starting >>> > date request would only apply to online imports for OFX and (I think, >>> but >>> > am not sure) aqbanking. >>> > >>> > Jack >>> >>> 4.8 is the latest stable release, and will probably get only important >> bug fixes if any changes at all. All current effort is going to complete >> the migration to Frameworks. If you followed the rest of the GPG >> Encryption email thread you started, Cristian said OFX import wasn't ready >> yet, I said I had tried it and it worked, and Thomas clarified that there >> were actually two separate parts to it - the one to do mapping was not yet >> migrated to Frameworks and the part to do the actual download was >> migrated. However, I would still not use the Frameworks version for >> production use quite yet. >> >> Right now, I suspect both versions would do the same thing with your >> Citibank download, so that's not a deciding factor. However, changing the >> behavior to handle this issue will likely be done in Frameworks >> (eventually) and not likely back ported to 4.8. >> >> >> >> >
