Scheduled Transactions / Since Last Run: Entry only selected transactions

[Dorel Ciornei]

I've been having questions along the same lines, so I am glad it was addressed here.Indeed, until you guys pointed it out, I didn't realize that the status of each line in the "Since Last Run" can be changed.This makes things a lot easier obviously.
Now when I just change the status of all lines to "Reminder" and leave as "To-Create" only the bill I want to pay.Seems to work ok that way.

I tried entering bogus transactions, but then I need a reminder to remind me to correct/enter the right transaction.
Side Note: I used Quicken for a few years, and the best feature and pretty much the only reason I stayed with it for that time was the Reminder feature.In my opinion, that feature was beautifully done. Being able to see the coming-up transactions (including the amount of each) in the actual calendar view was very helpful. 

Thank you again.Dorel C
 
      From: Jim Passmore <jim at passmore4.com>
 To: David Carlson <david.carlson.417 at gmail.com> 
Cc: gnucash-user at gnucash.org 
 Sent: Sunday, June 21, 2015 6:26 AM
 Subject: Re: Scheduled Transactions / Since Last Run: Entry only selected transactions
   
On Sat, Jun 20, 2015 at 12:14 PM, David Carlson <david.carlson.417 at gmail.com
> wrote:

>
> I am surprised that nobody has responded to this yet.
>

I actually had started a reply, but...


>
> The Since Last Run assistant is somewhat clunky


I'll say!  I'm a new user, and was going to give a big +1 to Old Samurai,
but then decided I should pull up GnuCash to verify a statement I had
written was correct, and it was only *then* that I discovered it's possible
to change the state from To-Enter to something else.  It's very non-obvious
there's anything to do there.  Also, the check-boxes are just begging to be
checked/unchecked, but you have to open the edit dialog to make a change?
Would be nice for the review-created-transactions checkbox to remember last
state rather than always unchecked...


> and there are several
> bug reports and suggestions for improvement that have languished because
> there are limited developer resources and those resources are being
> applied in other areas right now.


Wish I could help.  I know some Python and can read/tweak Java, but when it
comes to C I know nothing...


> There are work-arounds for most
> issues which other users have found.
>
> Generally, one work-around is to set a reminder with an early value
> large enough to satisfy your particular requirements for that case.
> Another that I have done in a few cases is to create a bogus transaction
> entry that is created early but serves only as a placeholder until the
> real transaction entry can be created.  I do that for utility bills that
> vary each month.
>

Realized that first approach could work, and how reminders work when I saw
that the status could be changed.  Seems pretty workable in my opinion.
Would never take the approach of creating a transaction to later correct,
though.  Without the scheduled transaction as a reminder I would forget to
go back and correct it!


>  In some older versions of GnuCash, the Postpone
> status did not work correctly, and I am not sure whether that has been
> fixed, I never use it.
>

Running ubuntu (xubuntu), soon to be upgraded to 15.04, and I will test
that.


>
>
> If you have any other questions, feel free to ask them here.  Other
> users or developers are usually here and able to help.  The chat page
> also usually has developers watching.  I use that myself from time to
> time.  Chatzilla is a nice client for that.
>
>
Probably be checking in on a couple mortgage & budgeting items...

Thanks!

-- 

*Jim Passmore*


_______________________________________________
gnucash-user mailing list
gnucash-user at gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.