https://bugs.kde.org/show_bug.cgi?id=524131
--- Comment #10 from Jack <[email protected]> --- That mostly makes sense, except for some details. I won't be able to confirm as I apparently have an older 5.1.3. appimage. Normally, merging two Payees deletes one and assigns all references to it to the other If it fails to reassign and leaves the reference present, you have what is actually an invalid file, although checking for that on consistency check and on file input was apparently only added in a (relatively) recent 5.2. What would be interesting to me is what is in the file saved by an early version of 5.2.2. I assume it is essentially the same as saved by 5.1.3, with the invalid references still present. Once the consistency check and input check were added, you can see the problem on import. Another curiosity is what happens if you run that report in the early version of 5.2.2. I would expect some error, since the report refers to a non-existing payee. Another solution would be to change all those reports to refer to "all payees." That would remove any explicit reference to the payeees, including the "missing" ones. If you did that in 5.1.3 or that early 5.2.2, then opening in a more recent 5.2.2 will have no need to recreate any payees. -- You are receiving this mail because: You are watching all bug changes.
