[kmymoney] [Bug 525369] Investment Performance Report misses a lot of columns in master snapshot

[Ralf Habacker]

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

Ralf Habacker <ralf.habacker at freenet.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WAITINGFORINFO
             Status|REPORTED                    |NEEDSINFO

--- Comment #5 from Ralf Habacker <ralf.habacker at freenet.de> ---
(In reply to Robby Engelmann from comment #3)
> I had an Investment Performance Report per year and one that covered all
> time. I had to re-create the report and now it works, however, I will not do
> that for all the years before.

With
https://invent.kde.org/office/kmymoney/-/commit/5c31d0a39f80fcabef2de93f8534be7619daac9d,
a design flaw in the definition of performance reports was fixed in the Git
master branch.

This fix searches report definitions for the following attributes 

    rowtype=“equitytype” querycolumns="performance"
    rowtype="topaccount-account"  querycolumns="performance"

and converts them to:

    rowtype="performancetype" querycolumns="performance"
    rowtype="performancetopaccount"  querycolumns="performance"

The fact that this fix was applied when loading a KMymoney file should be
indicated by the following tag in the header of the KMymoney file.

     <FIXVERSION id="12"/>

and in normal console output when running kmymoney from a console as:

    testing fileFixVersion 11 < 12
    2 reports(s)  fixed in fixFile_11

If this did not work for you, there must be a discrepancy in the file you are
using; for example, if FIXVERSION is already set to 12, this conversion will
not be skipped. Resetting it to 11 may help in this case.

If there are other historical performance report types that contain
`querycolumns=“performance”` but have a different `“rowtype”` than those listed
above, this could also cause the problem because they would no longer be
recognized as performance reports. If this is the case, please provide the
relevant report lines or at least the two attributes listed here so they can be
addressed accordingly.

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