| Summary: | Scheduled Transactions: Payee field not saved in transactions when there are multiple category splits | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | Paul Worrall <p.r.worrall> |
| Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 5.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Paul Worrall
2025-11-08 12:50:11 UTC
Confirmed I thought I had a hint about what is going on. but now I'm not sure. Note that when you create the scheduled transaction, the split editor looks like the split editor used in the Ledgers View (as it should, I think.) Note that when you close the split editor, the Payees on the splits are shown in the Memo column, there being no column displayed for Payees (also OK, as far as I can tell.) However, if you then re-open the split editor (before actually saving the Scheduled Transaction) the Payees are already gone. I have not yet looked into the code that actually saves the Splits within the Schedule, but I wonder if that is where they might be getting lost. I'll try diffing into the code. I think the relevant code is here: https://invent.kde.org/office/kmymoney/-/blob/master/kmymoney/mymoney/mymoneyschedule.cpp?ref_type=heads#L176 The comment a few lines earlier says it's clearing out some "unused information ... for the case that the transaction passed ... is a matched or imported transaction". I don't understand that, but the payee field is not "unused information" for the use case mentioned in my report. Also, it is inconsistent that you can populate the payee fields when entering a transaction manually but not via a schedule. In fact it is exactly this line https://invent.kde.org/office/kmymoney/-/blob/master/kmymoney/mymoney/mymoneyschedule.cpp?ref_type=heads#L186 which is older than 16 years and dates back to I don't know what. Maybe it's about time to change it a bit. |