[kmymoney] [Bug 405293] CSV importer does not handle transfers
https://bugs.kde.org/show_bug.cgi?id=405293 --- Comment #7 from Don S. --- This bug bit me too while trying to import a csv file that contains a lot of tranfers. I tried putting [brackets] around the account name in the csv file but that didn't work either. I hoped to be able to pre-process csv files and import into KMyMoney to save some time and errors but that doesn't seem possible since this bug has existed for more than 3 years. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405293] CSV importer does not handle transfers
https://bugs.kde.org/show_bug.cgi?id=405293 --- Comment #9 from Don S. --- Jack, I should have said 'impractical' rather than 'impossible'. It make my play to pre-process the csv files to save time every month impractical. But,, I just thought of a ?possible? workaround. I can put something in the csv Payee field and use KMyMoney's Payees Match and Default category. That's assuming that KMyMoney's csv import processes those rules when importing. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405293] CSV importer does not handle transfers
https://bugs.kde.org/show_bug.cgi?id=405293 --- Comment #11 from Don S. --- Good idea. Also, after years of using KMyMoney, I just realized that I can select multiple transactions and it can change their categories in one step. Using the filter to find them will make it even easier. But I'll try the other idea with the Payee processing tomorrow and let you know how it goes. I have to go somewhere, otherwise I'd try it now. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405293] CSV importer does not handle transfers
https://bugs.kde.org/show_bug.cgi?id=405293 --- Comment #12 from Don S. --- I just tried using Payee Matching to import a test file and that didn't work to create a transfer transaction. It didn't work. It created a new category like it did before. Jack: Your idea of entering a unique category in the csv and changing the transactions manually seems to be the quickest way to handle it. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 466356] New: Balance field not wide enough
https://bugs.kde.org/show_bug.cgi?id=466356 Bug ID: 466356 Summary: Balance field not wide enough Classification: Applications Product: kmymoney Version: 5.1.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: d...@donstrenzwood.com Target Milestone: --- SUMMARY When 2 transactions are matched, the transaction shows in a bold font. The Balance field in the ledger is not wide enough to show the entire number. For example, if the balance is "69,633.14", it will show the balance as "9,633.14", cutting off the "6". STEPS TO REPRODUCE 1. Enter two transactions with the same amount, like 7.99 2. Select them both and Match. 3. Look at the balance field. OBSERVED RESULT The balance displays incorrectly. EXPECTED RESULT To see the whole number. SOFTWARE/OS VERSIONS Windows: 11 ADDITIONAL INFORMATION It seems the width of the Balance field is based on the size of normal fonts and, when the font is bold, it's cropped. -- You are receiving this mail because: You are watching all bug changes.
