Bug 403402 - Payee matching/inputting isn't working properly when importing with OFX
Summary: Payee matching/inputting isn't working properly when importing with OFX
Status: RESOLVED NOT A BUG
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: git (master)
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-19 15:45 UTC by Michael Carpino
Modified: 2019-02-02 21:37 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Carpino 2019-01-19 15:45:08 UTC
SUMMARY 

When I import transactions using OFX some transactions don't match the specific previously used payee. It leaves the Payee blank for these transactions.  When I start typing the Payee the program doesn't match to any of the existing Payees and then wants to create a new payee.


STEPS TO REPRODUCE
1. Import transactions via OFX
2. Locate the transaction that doesn't have a Payee assigned. Type in the Payee field the Payee
3. Observe the program trying to create a new Payee 


EXPECTED RESULT  Program should match to a proper payee upon importing and/or upon entering a blank Payee enter/pull from the existing Payees available. 


SOFTWARE/OS VERSIONS

KMM AppImage Version 5.0.80-b17d61f
Operating System: Manjaro Linux 
KDE Plasma Version: 5.14.5
Qt Version: 5.12.0
KDE Frameworks Version: 5.53.0
Kernel Version: 4.20.1-1-MANJARO
OS Type: 64-bit
Processors: 4 × AMD A8-6410 APU with AMD Radeon R5 Graphics
Memory: 3.3 GiB of RAM
Comment 1 Michael Carpino 2019-02-02 14:41:59 UTC
After further looking at this issue I've noticed that the program is prepopulating the Payer/Receiver field in the ledger with a space when importing OFX transactions.  If you backspace in the Payer field you can then locate preexisting payers.  This prepopulated space is what appears to be causing the program to not match with an existing payer.
Comment 2 Thomas Baumgart 2019-02-02 15:16:53 UTC
Do you have a payee that only consists of a blank? What happens, if you get rid of it?

Can you turn on OFX and statement logging and provide what is found about the payee in both log files?
Comment 3 Michael Carpino 2019-02-02 16:13:17 UTC
I do have a blank payee.  I have deleted it and I will test the downloading of OFX transactions in a few days when I have some new items that become available.  I've turned on logging as well.  I'll provide an update as soon as I can.
Comment 4 Thomas Baumgart 2019-02-02 16:25:36 UTC
Do you know, that you can delete downloaded transactions and just get them again? This should work, if the transaction you delete is not older than one or two days. Otherwise, some settings tweaking might be necessary to get it again. I do this all the time for testing the HBCI download.
Comment 5 Michael Carpino 2019-02-02 21:36:09 UTC
Thank you, Thomas, for your tips and thoughts.

I was able to delete the OFX transactions then reinput them.  The problem was related to the blank Payee that I deleted and 6 or so transactions from a few years ago that I needed to delete/reenter.  Once I did this KMM is now working for me as it should be.  

I appreciate your help.
Comment 6 Michael Carpino 2019-02-02 21:37:43 UTC
Corrected my file and the programming is working as designed