Bug 463854 - When transaction is imported and match a configured Payee, the date info from Payee is lost
Summary: When transaction is imported and match a configured Payee, the date info from...
Status: RESOLVED DUPLICATE of bug 351535
Alias: None
Product: kmymoney
Classification: Applications
Component: importer (show other bugs)
Version: 5.1.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-04 23:09 UTC by Antoine T
Modified: 2023-09-07 21:51 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 Antoine T 2023-01-04 23:09:08 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
The Pay to field contains data info and when importing the OFX file, the Payee is replaced by the configured Payee, then the date info is lost.

STEPS TO REPRODUCE
1. Creates a OFX file containing
---
D12/12/2022
T-12.10
PCARTE 09/12/22 AGRCST            CB*4563
---
2. Creates a Payee that matches partially on "AGRCST".
3. Import the transaction


OBSERVED RESULT

Then the import of such event will create a transaction with "Pay to" field of "AGRCST". The date info "09/12/22" is then lost! Which is a critical info. MEMO field provided by bank is empty so it does not contain the date info too.

EXPECTED RESULT

An option when importing OFX to copy "Pay to" field to MEMO.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Jack 2023-01-04 23:30:02 UTC
I believe in master branch, the original field from which Payee was detected is included in it's entirety in the memo.  I don't know if there is any chance that this will be back-ported to 5.1 or not.  What date does the transaction end up having?  Also - saying the date is lost implies that there is a date field in the import which is lost.  What is actually lost is the full original content of the Payee field,  Have I understood correctly?
Comment 2 Antoine T 2023-01-04 23:46:59 UTC
(In reply to Jack from comment #1)
> I believe in master branch, the original field from which Payee was detected
> is included in it's entirety in the memo.  I don't know if there is any
> chance that this will be back-ported to 5.1 or not.  What date does the
> transaction end up having?  Also - saying the date is lost implies that
> there is a date field in the import which is lost.  What is actually lost is
> the full original content of the Payee field,  Have I understood correctly?

Exactly, the date lost is not the transaction date field, but the time of operation date, that is in the content of Payee field. You understood correctly.
Also, the mechanism should be an option in case there is already information in MEMO field provided by the bank.
Comment 3 Antoine T 2023-09-07 21:48:53 UTC
I am closing this ticket as I didn't see I have opened a duplicate ticket #351535 in 2015 (!).
Comment 4 Antoine T 2023-09-07 21:49:01 UTC

*** This bug has been marked as a duplicate of bug 351535 ***
Comment 5 Antoine T 2023-09-07 21:51:05 UTC
Please note that there is an error in the test scenario I have written in description. I said it is an OFX file while describing a QIF file. The test scenario of the issue is actually with a QIF file, because there is no issue with an OFX file.