Hi,
I use Kmymoney for years… 5.1.3 snap version on Ubuntu 22.04 and 24.04, and I try too with AppImage master version 4122, and I have the same problem :
the split transactions don’t appear in reports, by payees or by categories.
For example : for a transaction with 3 lines split with different categories and different tags, a report based on a category doesn’t show the line transaction with this category.
Is this a bug ? or where do I a mistake ?..
Thank you for your help.
I’ve run into exactly the same problem with generating reports showing tags in split transactions in Fedora 41. Have not found a workaround.
Do you experience the same problem when using the development version?
I hadn’t tried the development version when I posted the original comment.
Just downloaded and installed it, and the ‘tags’ in splits appears to work properly now, and the user interface is far improved from the previous version.
Excellent … thanks!
Thank you for this new release, but…
It doesn’t work for me.
Ubuntu 22.04 64 bits
Kmymoney Appimage Version 5.1.92-76ca71f
My transaction is split in 3 lines, with 3 different categories and 3 different tags (you can see it on attached picture “by-payee-test”, the 10th of february transaction).
When I create a new report (to be clean) based on default report “Transactions by Tag” (attached picture “by-tag”), I select one tag (“main courante blacon”), all dates, all everything… As you can see, the report shows the transactions repeated twice, without total, and missing one transaction, the line of the split transaction. The 10th february transaction is missing.
And at the begining, I wanted to make a report by category (attached picture “by-category”). I filtered all dates, all categories, all payees… all everything, but only “main courante balcon” tag. As you can see, my 10th february split transaction doesn’t appear in the report, and the Date column is trunked (the year is cut).
It seems that one line of a split transaction is bad filtered in a request.
If you want more details or my kmy file, I can send it to you in private.
Thank you for your help.
Thanks for the offer, but I was able to reproduce the problem. Unfortunately, the underlying reporting logic comes to its limits in your case which is not easily solvable without a major refactoring of the code. A respective bug report already exists.
OK, I can understand the problem (of refactoring the code).
Despite, could you suggest me a solution to turn around this problem ?
delete a too much tag ? delete a category ? or… what else ?.. to simplify the transaction to be selected in the report ?
It’s not a problem of the tags in the transaction, it’s a problem of the reporting filter which does not work properly when using a grouping by tag and a tag filter (which explains why you notice that the transaction with the tags dated 10/02/2025 is missing).
Maybe, exporting an unfiltered report to CSV and continue filtering using a spreadsheet application may get you further at this point in time.
I changed my way ; the category filter seems to work right.
So, I created a sub-category instead of using a tag ; and the report by category renders the result I wanted.
Thank you very much for your dedication.