[Kmymoney-devel] [kmymoney4] [Bug 335402] New: Prevent replacement of payee when importing transactions

[Allan]

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 at kde.org
>            Reporter: developerchris at 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