I have created scheduled transactions where "The amount is an estimate because it varies for each paiement" is ticked and the amount specified is 0. This amount is accepted and the scheduled transaction is saved without problem; however, if I edit the transaction, I cannot save it unless the amount is not 0. I wish to be able to edit a scheduled transaction and save it while maintaining the amount to 0 (provided the "amount .... estimate ..." box remains ticked) (I don't suppose it makes a difference but I am using the french translation of KMymoney)
Yes, this was a design issue. If the option "The amount is an estimate because it varies for each payment" is not ticked, an imported transaction is only matched if the amount matches exactly. If the option is ticked, a range of n % (I don't remember details about n from the top of my head) is allowed around the amount entered with the schedule. An amount of 0 does not make sense in this regard. To workaround your problem, use an amount of 0.01.
(In reply to Thomas Baumgart from comment #1) > An amount of 0 does not > make sense in this regard. > > To workaround your problem, use an amount of 0.01. My point is that it is perfectly possible to *create* a scheduled transaction with an amount of 0.... The issue is only when editing the transaction (therefore, my current workaround is to delete the scheduled transaction and create a new one... still with an amount set to 0)
I just tried this in 4.8.1 on Linux, and I am not able to even create a scheduled transaction with an amount of $0 whether or not I check for varying amount. Is there any reason this should be different on Windows? Are you trying to edit the scheduled transaction (to change something other than the amount?) or are you talking about actually entering a transaction? Thomas - I don't see why it should not be possible to create or edit a scheduled transaction and leave the amount zero. This does not have anything to do with matching, unless I am misunderstanding something about the request.
(In reply to Jack from comment #3) > I just tried this in 4.8.1 on Linux, and I am not able to even create a > scheduled transaction with an amount of $0 whether or not I check for > varying amount. Is there any reason this should be different on Windows? I am using version 4.8.0; dunno if it makes a difference (actually, I have been creating scheduled transactions with 0 amount for *years* with previous versions.) > > Are you trying to edit the scheduled transaction (to change something other > than the amount?) or are you talking about actually entering a transaction? > In fact, I always do the same mistake: when I wish to enter a transaction, I double-click on it (instead of right clicking, so I am in fact in the process of editing the scheduled transaction while I think I am entering a transaction); I set the date and amount, and (bingo!) I end up with an updated scheduled transaction with an amount that is no longer 0... and I cannot reset it to 0 Don't ask me why I insist on having a scheduled transaction with 0 amount :-). I am used to do it this way, they are sort of "highlighted" in the list and since the amount is highly variable, using 0 is the most sensible value (IMHO). I was curious to understand the different behavior of the software when creating or when editing (and pleaaaaaaase do not make it consistent by removing the possibility of creating a scheduled transaction with 0 amount!)
(In reply to Philippe Martin from comment #4) *update* it appears that, as of 4.8.1 on Windows, it is no longer possible to create a scheduled transaction with 0 amount :-(((((
Git commit 744fc7c6e35a17e553c10c68f0780d3a3c6f5a05 by Thomas Baumgart. Committed on 24/01/2018 at 21:25. Pushed by tbaumgart into branch '5.0'. Allow schedules with amount being zero M +2 -3 kmymoney/dialogs/keditscheduledlg.cpp https://commits.kde.org/kmymoney/744fc7c6e35a17e553c10c68f0780d3a3c6f5a05