https://bugs.kde.org/show_bug.cgi?id=427519
--- Comment #4 from Jack <ostrof...@users.sourceforge.net> --- Since you have done successful merges before, my guess is there is some problem with a transaction for one of the Payees to be deleted, which interrupts the reassignment of transactions to the chosen Payee. Again, only a guess, but I wonder if something other than the Payee-id is changed in a transaction, which is then left in some invalid state, no longer associated with any payee. In any case, a few more questions to help troubleshoot. If you do the merge, and then save the file (or maybe just run a consistency check) does KMM complain about anything related to the merged payees or the missing transactions? Can you find any of the missing transactions by looking in the ledger for the relevant account and date? Here I'm wondering if the transactions are actually still present, but there is only some problem in the display in the Payees View. Have you ever saved the file (to a new name so you don't overwrite your good backup) and then opened it again? Can you save an anonymized version of the file? If so, can you identify the three payees to be merged, and which one you want to keep? In the anonymized files, Payees are just named by their internal ID, so for example, you can do 'grep "PAYEE.*PetSmart" file.xml' or 'zgrep "PAYEE.*PetSmart" file.kmy' to find the id for that Payee. If you can replicate the problem with the anonymized file, there is a better chance of myself or one of the developers identifying the underlying problem. -- You are receiving this mail because: You are watching all bug changes.