] Template Transactions Behavior in Scheduled Transaction Editor
Hello,
Long time user working in Windows 10 with Gnucash 4.13.
I have a number of scheduled transactions that I use; one of them has multiple
splits. With the new year, I needed to update this scheduled transaction. I
began
On 12 January 2024 at 23:36, Adrien Monteleone said:
> That's moving beyond Scheduled Transactions and into a more general case
> of Templates. I'm pretty sure I've already filed an RFE for that long ago.
>
> I see Scheduled Transactions as a special use case of Templates, though
> Scheduled was
Not general templates, no. It only has scheduled transactions.
There is a request for templates.
Regards,
Adrien
On 1/12/24 11:56 PM, R Losey wrote:
I'm sensing a learning opportunity here... GnuCash has templates? I never
noticed that; I only use the templates in the Scheduled Transaction
I'm sensing a learning opportunity here... GnuCash has templates? I never
noticed that; I only use the templates in the Scheduled Transaction Editor.
On Fri, Jan 12, 2024 at 11:37 PM Adrien Monteleone <
adrien.montele...@lusfiber.net> wrote:
> That's moving beyond Scheduled Transactions and into
That's moving beyond Scheduled Transactions and into a more general case
of Templates. I'm pretty sure I've already filed an RFE for that long ago.
I see Scheduled Transactions as a special use case of Templates, though
Scheduled was implemented first.
The more general Template case is when
Liz,
Since you asked, I think that is a good idea. We could have both a test
run while editing that did not crash anything if it failed and when looking
at the SX but not editing it, have a button that triggers the creation of
the next instance. That would probably work regardless of the SLR
>From the pulldown menus:
Actions -> Scheduled Transactions -> Since Last Run...
> On 01/12/2024 7:13 PM PST Liz wrote:
>
> So would you like a button which gives an option to make a test run?
>
> Liz
>
> On Fri, 12 Jan 2024 12:08:14 -0600
> David Carlson wrote:
>
> > I consider the SX to
On Fri, 12 Jan 2024 12:08:14 -0600
David Carlson wrote:
> I consider the SX to be a graphical form of a script, and so I am not
> sure how the editor could detect what is safe to call an expression
> that could be evaluated while it is being edited.
>
So would you like a button which gives an
Stan,
Scheduled transactions [SX's] are only executed when the Since Last Run
assistant is triggered, and then only when they meet several criteria such
as the calendar date matching the scheduled execution date but the SX is
not postponed or ignored. Some users, like myself, have as many as
ary 12, 2024 2:21 PM
To: gnucash-user@gnucash.org
Subject: Re: [GNC] Template Transactions Behavior in Scheduled Transaction
Editor
On 2024-01-12 08:17, Adrien Monteleone wrote:
> I am not unsympathetic to that conundrum!
>
> On 1/12/24 12:23 AM, David T. via gnucash-user wrote:
>>
On 2024-01-12 08:17, Adrien Monteleone wrote:
> I am not unsympathetic to that conundrum!
>
> On 1/12/24 12:23 AM, David T. via gnucash-user wrote:
>> if I have to remember to run the SLR in order to have them created,
>> then I've just changed the work, not reduced it.
I'm confused. I'm not
Thanks all for the discussion. I can rest easy knowing that this is how the SX
editor works. It just took me by surprise...
David T.
On Jan 12, 2024, 7:09 PM, at 7:09 PM, David Carlson
wrote:
>I consider the SX to be a graphical form of a script, and so I am not
>sure
>how the editor could
I consider the SX to be a graphical form of a script, and so I am not sure
how the editor could detect what is safe to call an expression that could
be evaluated while it is being edited.
On Fri, Jan 12, 2024, 11:36 AM Adrien Monteleone <
adrien.montele...@lusfiber.net> wrote:
> What I meant
What I meant was it would indeed be nice that the SX Template entry
allowed you to do math like a register does.
I never meant to imply that one could edit the code from within the app!
Regards,
Adrien
On 1/12/24 11:27 AM, David Carlson wrote:
I beg to differ. Executing code while editing
I beg to differ. Executing code while editing it would be an invitation to
disaster.
On Fri, Jan 12, 2024 at 10:25 AM Adrien Monteleone <
adrien.montele...@lusfiber.net> wrote:
> Indeed, I should have tested it prior to commenting.
>
> Apologies for the noise.
>
> At the very least, being able
Indeed, I should have tested it prior to commenting.
Apologies for the noise.
At the very least, being able to do math here with a result would be a
good RFE.
I would only expect formulas to remain as formulas if they contain
variables which require a prompt for value.
Regards,
Adrien
On
I am not unsympathetic to that conundrum!
Regards,
Adrien
On 1/12/24 12:23 AM, David T. via gnucash-user wrote:
if I have to remember to run the SLR in order to have them created, then I've
just changed the work, not reduced it.
___
gnucash-user
By "manually enter" I mean to trigger the entry into the register of the
next scheduled instance of a single scheduled transaction [SX] without
invoking the Since Last Run druid. I would expect that to be an action
available in the SX editor.
Since one SX may contain more than one separate
I'll look into these options. I just have it in my head that the point of a
scheduled transaction is to save me from having to remember to create a
transaction, and if I have to remember to run the SLR in order to have them
created, then I've just changed the work, not reduced it.
But thanks
I am pretty sure I tried that, but it didn't actually do the calculation in the
SX window. Which makes sense, I think, because that window allows formulas that
get processed at runtime.
David T.
On Jan 11, 2024, 8:46 PM, at 8:46 PM, Adrien Monteleone
wrote:
>You don't have to do it in
What do you mean by "manually enter a SX?"
Regards,
Adrien
On 1/11/24 4:19 PM, David Carlson wrote:
I think that we need to see how SX's will work after the Since Last Run
druid is fixed before proposing more improvements. If I understand
correctly, there is an unresolved issue preventing
I think that we need to see how SX's will work after the Since Last Run
druid is fixed before proposing more improvements. If I understand
correctly, there is an unresolved issue preventing nightly builds, so it
will be difficult to test anything right now anyway.
As for balancing SX's, I often
That sounds like you have an SX to autocreate. Perhaps turn that off and
it won't fire.
Otherwise, perhaps turn off the preference to execute the Since Last Run
dialog on startup. You can still run it manually to fire any pending
SXs, but otherwise, not have it bother you if you just want to
You don't have to do it in your head.
While an extra step compared to normal registers, you can still do math
on a split.
When entering that balancing split, enter the amount as a sum formula.
(split one amount + split two amount, etc.) GnuCash will give you the
overall sum.
Regards,
I would guess that the code for calculating the balancing amount as the
sum of the other splits is part of the code that forces the transaction
to be balanced before committing.
Since SXs don't have this rule, that code to sum the other splits never
gets executed.
Regards,
Adrien
On
I've found the "Prompt for value" option with SXes to be downright annoying.
I go to Gnucash to check the balances in a savings account, and the SX dialog
pops up asking me for a dollar amount for my electric bill (and won't seem to
let me just click past). Inevitably, I just put in any old
On 2024-01-11 12:55, David T. via gnucash-user wrote:
> Long time user working in Windows 10 with Gnucash 4.13.
>
> I have a number of scheduled transactions that I use; one of them
> has multiple splits. With the new year, I needed to update this
> scheduled transaction. I began modifying the
Hello,
Long time user working in Windows 10 with Gnucash 4.13.
I have a number of scheduled transactions that I use; one of them has multiple
splits. With the new year, I needed to update this scheduled transaction. I
began modifying the amounts on different lines of the transaction, and
28 matches
Mail list logo
