[kmymoney] [Bug 470384] CSV save of data from transaction by category report omits category name on total line for that category

[bugzilla_noreply at kde.org]

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

--- Comment #3 from m.a.stelman at spectrum.net ---
Sorry, had to create a second account to accommodate second email 
address I use.



-------- Forwarded Message --------
Subject:        Re: [kmymoney] [Bug 470384] CSV save of data from transaction 
by category report omits category name on total line for that category
Date:   Tue, 30 May 2023 00:01:15 -0700
From:   Michael Stelman <m.a.stelman at spectrum.net>
Reply-To:       m.a.stelman at spectrum.net
To:     bug-control at kde.org



Jack, thank so much for the prompt reply, and making KMyMoney such a 
useful tool I have enjoyed for many years.  After further testing v5.1.3 
I was able to clarify the extent of the problem and narrow the 
particular features affected which I submitted in an online comment to 
your comment with an additional screenshot to illustrate, both also 
attached to this email reply.

Perhaps in your reply  you are referring to the pending v5.2 release 
when you said: 'If "hide transactions" is set in the report 
configuration, the category names ARE shown, but that is then the only 
line for that category.'

In my experience with v5.1.3: 'If "hide transactions" is _deselected_ in 
the report configuration, the category names ARE shown, but that is then 
_only on the top line preceding the itemized list of transactions and 
the unlabeled subtotal on the bottom line_ for that category.'

In my testing, it affects Reports for Transactions, Investments, and 
Taxes.  And in those report groups, it affects all individual reports by 
Account, Category, Payee, or Tag.

Sorry I waited so long and just got around to updating to v5.1.3 - 
version 4.4 worked so well for me that I never bothered to update sooner.

Sincerely, Michael Stelman.

Attachments: copy of comment submitted to 
https://bugs.kde.org/show_bug.cgi?id=470384

Clarification of prior bug report “[kmymoney] [Bug 470384]”

Subject: v5.1.3 Reports exported as .csv filetype fieldname labels are 
omitted on subtotal lines, was not a problem in v4.4.

Longtime fan of KMyMoney deeply appreciative of all developers efforts 
to provide this valuable tool, and receptiveness to users submissions of 
bug reports.

KMyMoney v5.1.3
Left menu bar: “Report”
“3. Transactions” OR “5.  Investments” OR “6.Taxes”
“<reportType> by Account OR Category OR Payee OR Tag”
“Export” button function
Dialog box “Export as”
Dropdown selection box “Save as type”
Selection “CSV document (*csv)”
Output .csv file

If user configures: “Rows/Columns” selecting “Hide Transactions”, output 
file consists of a single column of listed subtotals without any 
fieldnames identifying the account, category, payee, or tag being 
subtotaled.

If “Hide Transactions” is deselected, fieldname is printed in row at top 
of itemized transactions, and subtotal is printed at bottom of its 
itemized transactions, but was clearer in v4.4 when subtotal amount was 
preceded on same line by fieldname.

Interestingly, I accidentally discovered that if the Report is exported 
as .html filetype, the problem is not encountered.

See attached screenshots of two examples.

On 5/29/2023 5:12 PM, Jack wrote:
> https://bugs.kde.org/show_bug.cgi?id=470384
>
> Jack<ostroffjh at users.sourceforge.net>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Severity|major                       |normal
>              Summary|CSV export omits category   |CSV save of data from
>                     |field name                  |transaction by category
>                     |                            |report omits category name
>                     |                            |on total line for that
>                     |                            |category
>               Status|REPORTED                    |CONFIRMED
>       Ever confirmed|0                           |1
>
> --- Comment #1 from Jack<ostroffjh at users.sourceforge.net>  ---
> It took me a while to figure out what you are talking about.  Unfortunately,
> there is a terminology issue, in that we do not call this a csv export
> (File/Export/CSV,) which is only done one account at a time.  However, given
> that the screen labels do say export the data for a report I can see the
> terminology problem.  We'll have to find a way to avoid this confusion in the
> future.  We would call this saving the data from a transaction report.  From
> the screenshot I see it is the Tax Transactions by Category last Physical Year.
>   It probably applies to all transaction by category reports, tax related or
> not.
>
> Just as a side note, it's a bit late to be reporting this as a regression from
> version 4.x, which hasn't been supported in many years.  However, it is
> certainly a reasonable request.  I've altered the priority from major to
> normal, as it is really a convenience issue which would make the saved data
> more easily readable, but does not result in incorrect data.  I'll leave it at
> that, instead of a wishlist.  Until I look into the code, I don't know how easy
> this actually is to implement.  Unless it is an easy fix, it will likely be
> deferred to 5.2 (which is the label we are using for when the master
> development branch is released for production use, which is not yet scheduled.
> 5.1 is only getting fixes to bugs that affect the data or cause crashes.
>
> For summary, in csv export of data from Transaction by Category Reports (only
> confirmed in Tax Report so far, but likely all) the summary line showing the
> total amount for a category does not repeat the name of the category, making it
> harder to interpret.  In master branch, the total is put in the right most
> column, which helps a small bit, but the category name is still omitted.  If
> "hide transactions" is set in the report configuration, the category names ARE
> shown, but that is then the only line for that category.
>

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