Actual Development of KMyMoney

Hi KMyMoney team,

Development version 5.1.80-8233074 from December 18th, 2024

  1. Is it no longer possible to enter entries line by line in split entries, but only with the “formular”?

  2. Is it correct that when opening an account view, the entries from the beginning (e.g. 2014) are always displayed and I have to click on the entries with a mouse click and then press key “End” to get to the current entries?

  3. Is it correct that documents still cannot be attached to entries?

  4. Is it correct that the reports still do not have a function to drill-down to the relevant entries?

If points 1 and 2, then that is a huge step backwards.

If points 3 and 4, then that is not progress.

greetings
Udo

  1. Yes
  2. No - for me it opens the ledger and selects the most recent transaction (which is at the bottom if sorted by ascending date)
  3. No - see the commit message how this is used
  4. Yes (except some reports)

For #2, for me most ledgers open at the newest transactions (bottom) but all investment accounts still open at the oldest (top.)

Hi Thomas,

  1. No - see the commit message how this is used

OK… I unfortunately overlooked that. Shame on me…

My last development was version 5.1.80-867d995 from October 28th, 2024, and this function was not included there.

I see in the KDE GitLab that it was added on October 30th.

I remember that Ralf Habacker designed something there two years ago, and this is now implemented.

I have to look again at how it works.

greetings
Udo

Hi,

I’ve taken a look at Link Matching now.

If I’m wrong, please correct me.

a) I have to enter the patterns for the identifier and the URL for EVERY Payee.

It would make sense to have a general entry and for Payee only possibly different patterns.

b) I have to enter the file link manually in the memo field (so no selection menu)

c) Unfortunately, the whole thing doesn’t work with, for example, two links. Only the first one is opened.

d) I can’t find a way to select records with URL (or it’s extremely cumbersome if I know the content of the link)

By the way … pdf doesn’t work for me in the Appimage ("The Okular component was not found: The dynamic library could not be found).
txt or png, for example, works.

Summary: I can live with b) and d)
but a) the fact that I have to store the “standard pattern” for EVERY Payee… that’s a lot.

But this function is new in version 5.2 and will certainly be optimized.

greetings
Udo

Please check if this commit improves it for you.

Thanks. All accounts (including investment accounts) now open scrolled to the newest (bottom) transaction.

Sorting works now with Version 5.1.90-12e528e from December 19th.
(It works not with Version 5.1.80-8233074)

greetings
Udo

I’m not sure what your point is? 12e528e refers to the commit that fixed the issue. 8233074 is from several days earlier, prior to the fix being applied, so I would not expect it to work. I’m not sure if you are aware that those numbers are the most recent git included in that version. Apologies if you know this and are just pointing out that it didn’t work on Wednesday, but does work now.

Is there a response about the poster’s original enquiry? About having to enter a pattern for every payee? This seems to be contrary to the intent of payee matching by partial payee name. I thought I could add a partial payee name for one instance of the payee, (i.e. replace “payee name unique transaction id” with “payee name”) and assign a category to it, and then every instance of a transaction with “payee name” in the payee field would be assigned the specified category. But this doesn’t seem to work. This seems odd, because it would seem to imply that, every time a new transaction is imported for that payee, and the payee name has a unique transaction id in it, it will not match, and I will have to manually update the pattern matching again. It would be easier to just manually update the category for the transaction, and ignore pattern matching completely.
I’m confused!
:-\

I don’t see this any question about payee pattern matching in this thread. What am I missing?