Bug 369449 - <CATEGORY> line in ofx file imported switches payee to MEMO
Summary: <CATEGORY> line in ofx file imported switches payee to MEMO
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.8.0
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-27 21:41 UTC by Bob Ewart
Modified: 2022-11-23 05:17 UTC (History)
1 user (show)

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 Bob Ewart 2016-09-27 21:41:20 UTC
File->Import->OFX
Chase credit card ofx downloads recently added a blank <CATEGORY> line to a transaction.
<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>201609...[0:GMT]
<TRNAMT>-nn.nn
<FITID>201609...
<NAME>AMAZON MKTPLACE PMTS
<CATEGORY>
<MEMO>null
</STMTTRN>
In this case, the payee is 'null'.  If the <CATEGORY> line is removed, it is imported with 'AMAZON MKTPLACE PMTS' as payee

Note: When you are not doing online import, you don't have the option of what field to use as payee

Reproducible: Always

Steps to Reproduce:
1. Add a <CATEGORY> line to one transaction between <NAME> and  <MEMO> lines
2. File->Import-OFX
3. select the test file

Actual Results:  
The payee is shown as whatever is in the MEMO

Expected Results:  
Should always be what is in the NAME

If there is no MEMO line the payee is set to the NAME field even if there is a CATEGORY

I'm running 4.8.0 compiled from source on openSUSE 13.2.  It also happened on 4.72.
Comment 1 Justin Zobel 2022-10-24 00:46:41 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-11-08 05:10:55 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-11-23 05:17:24 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!