Schedule transaction gets entered on the correct date into the ledger (e.g 7/31/18). However, the date for the transaction increments to the current date - the 7/31 transaction will always show with the current date. If I look at the scheduled transaction after 7/31, it still shows the next due date of 7/31. I cannot change the date in the ledger. I need to delete the scheduled transaction from the ledger and enter a manual transaction. This has happened with every scheduled transaction I have. Running on Linux Mint 19
I don't think I understand what the problem is. A scheduled transaction can only be edited on the Schedules View - but that edits the schedule, which affects future instances. Once the scheduled transaction (say the last day of every month) is entered, it becomes a real transaction on 7/31, and that date will never change unless you edit it in the ledger. Once that happens, then the schedule should show the next instance as 8/31. Although future scheduled transactions may be shown in the ledger, you cannot edit them there, because they are not yet real transactions. Also, when you enter a schedule, you can alter the details (date, amount, payee, ...) and it should prompt whether you want those changes to apply on to this single instance, or to the schedule itself, thus for all future instances.
Jack probably described what you need to do. Select it with the right mouse button to open the context menu and select "Enter next transaction". Also, the scheduled transaction should appear grayed in the ledger. BTW, there is an option that allows you to enter due schedules automatically at program start. You may want to take a look at the manual for more details about entering scheduled transactions at https://docs.kde.org/stable4/en/extragear-office/kmymoney/details.schedules.entering.html Please report back if that helps.
Please let us know if the suggestions helped, or if you still have the problem.
Created attachment 117669 [details] attachment-26246-0.html Just happened again this month. The scheduled txns are set up to automatically be entered in the ledger, which they are. However, once there the txn never becomes 'current' and therefore can't be edited. May have something to do with the scheduled date not being a weekday. I'll try to pay closer attention next time it happens rather that just fixing it by deleting the scheduled text and entering a manual txn. Sent from BlueMail On Jan 26, 2019, 18:56, at 18:56, Jack <bugzilla_noreply@kde.org> wrote: >https://bugs.kde.org/show_bug.cgi?id=397094 > >Jack <ostroffjh@users.sourceforge.net> changed: > > What |Removed |Added >---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > CC| |ostroffjh@users.sourceforge > | |.net > Resolution|--- |WAITINGFORINFO > >--- Comment #3 from Jack <ostroffjh@users.sourceforge.net> --- >Please let us know if the suggestions helped, or if you still have the >problem. > >-- >You are receiving this mail because: >You reported the bug.
Created attachment 117678 [details] The schedule In the first step I create a schedule which today (2019-01-27) is overdue for two days. The option "Enter this schedule into the register automatically when it is due" is turned on (important).
Created attachment 117679 [details] The schedule in the ledger If you switch to the ledger of the account the transaction is shown with todays date. This is the standard behavior. It is grayed out to identify a schedule that is due but not yet issued.
Created attachment 117680 [details] Automatic check upon application start This option needs to be turned on so that the schedules are checked at application start. A setting of 0 days in advance will enter them exactly on the date they are due.
Created attachment 117681 [details] Restart the application In this state when the application starts it detects a schedule that needs to be entered and informs the user. It is still shown grayed out in the ledger. Then press OK to see the next dialog.
Created attachment 117682 [details] Enter the details of the transaction You can now enter the details of the transaction. The date is set to the actual due date. I left it here as is to see a change in the ledger and simply pressed Enter. If you change anything here, you will be asked if this is a one time change or should be used for future transactions.
Created attachment 117683 [details] Real transaction in ledger Et voilà the transaction is now stored in the ledger with the date we wanted and it is not grayed out anymore (because it's not a scheduled transaction but a real one). The date of this transaction does not change without user intervention.
Created attachment 117685 [details] Updated schedule Since the transaction was entered, the schedule was updated to the next due date. The question now is: what is the problem? For me everything works as designed.
Thomas, My scheduled transactions are all set up exactly as you outlined in your stream of emails. I only have an issue once in a while (still trying to figure out pattern) and only with a single schedule (I probably have 20-30 set up). I have 2 scheduled transactions set up as loan repayments and the problem appears to be related to that. Actually, I said I only had an issue with a single schedule, but the two loan schedules are very similar, so it could be either one or both of those. Either way, I have no issues with other types of transactions. At this point I'm thinking of just eliminating this type of scheduled transaction and making it a simple withdrawal or transfer. I don't require any further action from you on my behalf. I'm going to leave it as-is for now. If I see this happen again I'll try to note all the circumstances and forward to you. Thanks for looking into this. George On 1/27/19 8:59 AM, Thomas Baumgart wrote: > https://bugs.kde.org/show_bug.cgi?id=397094 > > --- Comment #11 from Thomas Baumgart <tbaumgart@kde.org> --- > Created attachment 117685 [details] > --> https://bugs.kde.org/attachment.cgi?id=117685&action=edit > Updated schedule > > Since the transaction was entered, the schedule was updated to the next due > date. The question now is: what is the problem? For me everything works as > designed. >
George, I'm still not sure exactly what the problem is. When a scheduled transaction is actually entered, it becomes a real transaction in the relevant account, and you can do anything with it that you can do with any other transaction. Before that, it is only a scheduled transaction, and although it is displayed in the relevant ledgers, you cannot edit it there until it has been entered. Up until the scheduled date, it should show the scheduled date, but after that date, since it has not been entered yet, it shows the current date, which will be the date of the transaction if entered then. I'm going to close this as WORKSFORME, but do reopen it if the problem happens again, especially if you can provide more details about what seems wrong.