I don't think I suggested you thought otherwise but since you've quoted me in your reply you must think that I did. I was simply replying to Gyles comment along the lines of the following.
Regards David H. Instead of having 11 or 12 sx templates, why not have one that fires monthly? Sent from Samsung Galaxy smartphone. On Thu, 18 Jan 2024 at 13:10, Adrien Monteleone < adrien.montele...@lusfiber.net> wrote: > I understood the OP referenced already created future transactions. > > No matter what, those have to be manually and individually edited > because they were already created. > > I can't imagine an auto-updating template being implemented. > > The solution would be to use a variable, and then not have them created > so far in advance of the likelihood of that variable changing. > > Regards, > Adrien > > On 1/17/24 1:08 AM, David H wrote: > > * think * not honk - spellcheck? Fat fingers ? > > > > On Wed, 17 Jan 2024 at 5:07 pm, David H <hell...@gmail.com> wrote: > > > >> I honk he’s talking about having 1 template but the transactions have > >> already been created 12 months in advance. I.e. he wants to update the > >> created tens based on an updated template after the fact. > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > 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. > _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: 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.
