| Summary: | importing gnucash makes payee from comment instead of corresponding account | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | M G Berberich <kde> |
| Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | RESOLVED WAITINGFORINFO | ||
| Severity: | normal | CC: | karel.aab, ostroffjh, tonyb.sfkde |
| Priority: | NOR | ||
| Version: | 3.98.x | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
M G Berberich
2011-05-29 17:30:44 UTC
Did you try with a newer version of KMyMoney (4.3.5 is the current stable)? 3.98 is outdated. I think this happens with data imported into Gnucash from bank statements. Try the 'Transaction Notes' import option as per manual extract below. Perhaps we should try to think of a better name for this option. Transaction Notes option Under some usage conditions, non-split GnuCash transactions may contain residual, often incorrect, memo data which is not normally visible to the user. When imported into KMyMoney however, due to display differences, this data can become visible. Often, these transactions will have a Notes field describing the real purpose of the transaction. If this option is selected, these notes, if present, will be used to override the extraneous memo data. This happens with transactions that have been manually entered in gnucash. (In reply to comment #3) > This happens with transactions that have been manually entered in gnucash. I think that what Tony actually means is that you try to import that file with the fourth option from the bottom of this dialog http://kmymoney2.sourceforge.net/kde4/online-manual/gnucash-import_options.png activated. The following is an extract from the manual re GnuCash import: Payees KMyMoney prefers that all transactions have a Payee (a generic term that encompasses both payees and payers), and unlike GnuCash, a list of these payees is maintained. Payee names are generated by the importer from the GnuCash transaction's Description field. This has proved satisfactory for some time now, with the option to over-ride in some circumstances, as detailed in my previous post. Any news? Changing state due to missing feedback Is it possible to edit multiple transaction data with these custom settings: 1. Copy data from payee field to Memo field 2. rewrite payee data with new custom name, so we can delete these useless payees. This would solve the problem and transaction data will not be lost You might get some similar effect by re-importing the data from scratch, with appropriate payees already set up, using the matching section for payees. Now, it seems your best approach is to delete those "wrong" payees - when you delete a payee, KMM asks to what other payee it should move the transactions. There is also a checkbox on that dialog to automatically add the old payee name as a matching string for the payee to which you move the transactions. |
