https://bugs.kde.org/show_bug.cgi?id=507416

Luke <kde-...@luke.fastmail.us> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #13 from Luke <kde-...@luke.fastmail.us> ---
(In reply to Thomas Baumgart from comment #12)
> Git commit 0d0783479b0375c243aff7126ddfd210476a632c by Thomas Baumgart.
> Committed on 24/08/2025 at 10:24.
> Pushed by tbaumgart into branch '5.2'.
> 
> Use correct method to determine top level parent id
> 
> In case an account referenced an unknown parent account duing loading,
> it needs to be reparented to the corresponding top level account group.
> The logic to determine that top level account group did not work as
> expected so that an empty account id was used, which caused problems
> (crashes) later on. This change now uses the new method to get the right
> parent id.
> (cherry picked from commit 1ef8bc926b93f2e4fbe73319f3d4a49c79d11629)
> 
> M  +11   -7    kmymoney/mymoney/storage/accountsmodel.cpp
> 
> https://invent.kde.org/office/kmymoney/-/commit/
> 0d0783479b0375c243aff7126ddfd210476a632c

The solution you provided via email relative to the extrusions/corrupted
categories in the history of the file do appear to fix the crash, and it does
let me open both the real file and the anonymous file without crashing, but all
of the accounts that are under institution I used prior to migrating to
kmymoney are not visible in the app. I'm happy to open a distinct bug, but I
think all of these are tied to the same root cause of lack of a strong way to
normalize IDs and names from imported files.

In this case all of the institution have IDs and names that are of the form
"#-bank" where # is a number.
A global find and replace in my XML file that converted  #-bank to "I10000#", a
similar replace for #-account, and #-category into unique account IDs appears
to restore the file relative to the master appimage build, but I suspect the
real trick here is to either make the logic behind the well-formed-ness of "ID"
fields more agnostic to the exact form these might have taken in the past, and
provide a mechanism to re-normalize them for the future.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to