Bug 335402

Summary:	Prevent replacement of payee when importing transactions
Product:	[Applications] kmymoney	Reporter:	Chris <developerchris>
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED WORKSFORME
Severity:	wishlist	CC:	cloutier.jo, ostroffjh
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Other
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Chris 2014-05-27 08:30:30 UTC

When importing the data can be very unstructured my bank has no concept of a payee it just has a memo field that field can can contain important data.

When importing if a match is found with a payee that information is replaced with the payee information

Thus the data is lost.

I suggest when the payee is not an exact match that the original payee field be placed into the memo field possibly concatenated to whatever is already there.

Reproducible: Always

Comment 1 allan 2014-05-27 09:51:07 UTC

On 27/05/14 09:30, Chris wrote:
> https://bugs.kde.org/show_bug.cgi?id=335402
>
>              Bug ID: 335402
>             Summary: Prevent replacement of payee when importing
>                      transactions
>      Classification: Unclassified
>             Product: kmymoney4
>             Version: unspecified
>            Platform: unspecified
>                  OS: other
>              Status: UNCONFIRMED
>            Severity: wishlist
>            Priority: NOR
>           Component: general
>            Assignee: kmymoney-devel@kde.org
>            Reporter: developerchris@rebel.com.au
>
> When importing the data can be very unstructured my bank has no concept of a
> payee it just has a memo field that field can can contain important data.
>
> When importing if a match is found with a payee that information is replaced
> with the payee information
>
> Thus the data is lost.
>
> I suggest when the payee is not an exact match that the original payee field be
> placed into the memo field possibly concatenated to whatever is already there.
>
> Reproducible: Always
>

You say elsewhere that mainly you use the CSV importer.  That importer 
has the capability to copy the chosen memo field to the payee field, or 
vice versa.  It sounds like that might help you.

When selecting fields, having selected the payee field, choose that same 
field as the memo field.  You will be told it is a duplication, but 
asked if you wish to make the copy.  If you choose yes, the copy occurs. 
If not, you go back to the duplication to choose different columns.  If 
you've chosen the memo field first, a similar process may be followed.

Allan

Comment 2 Chris 2014-05-27 12:37:51 UTC

I wasn't aware of that little tip

I had noticed that when you select a column that has already been selected it clears both selections. I obviously never tested the payee and memo columns.

Thanks Allan that's brilliant.

Comment 3 Jack 2014-05-27 13:44:27 UTC

I believe this problem does not occur with the OFX importer (file or direct) as you can configure which field is used to indicate the payee, but if it's the memo field, the memo field keeps the original value.

Comment 4 Jonatan Cloutier 2014-06-04 03:51:04 UTC

(In reply to comment #3)
> I believe this problem does not occur with the OFX importer (file or direct)
> as you can configure which field is used to indicate the payee, but if it's
> the memo field, the memo field keeps the original value.

I confirm that In version 4.6.4 the memo field keep it's value if it has one and thus the original payee is lost. would be grate if the would be concatenate.

Comment 5 Thomas Baumgart 2018-09-08 12:13:12 UTC

In case you want to keep the payee then don't select the memo field as the source. That completely defeats the purpose. Since the original problem was solved, I close the entry.