https://bugs.kde.org/show_bug.cgi?id=374352
--- Comment #18 from Peter J. Farley III <pjfarl...@earthlink.net> --- I would be happy for a solution that required me (the end user) to signal "do not match this Payee, take it literally as written", perhaps with a leading special character that would not normally appear in Payee names (perhaps tilde, "~", for instance). The import process would remove the leading special character and store the remainder of the Payee field as-is and mark that Payee as "Do not match" if it is a new Payee. For users like me who need to pre-process CSV imports anyway, such a solution is not a lot of additional effort and is a reasonable solution to the problem which does not break any existing Payee matching procedures. However, even with this solution I can see a potential issue for CSV exports. In order to be useful to re-create an entire account, the Payees marked "Do not match" would need to have the "special character" added to at least the first occurrence of that Payee in the export file, and that may break or at least annoy users who export to CSV and expect to see exactly what is in the base file. To avoid that export issue may require an option on CSV export to mark the first "Do not match" Payee with the "special character" or not, defaulting to NOT add the character, and requiring users like me to check that option to get the results that we desire. I also have not considered what QIF/OFX imports and exports should or should not do, since I am not dealing with those formats at the moment. I would think they have the same issue as I have reported, and may need the same solution (whatever that may become). Peter -- You are receiving this mail because: You are the assignee for the bug.
