Ok David so what are you changing on your template that you want to update to your already created txns ? Is it just a changed amount, are you adding further splits, making significant changes ?
A bit roundabout but this is how I would handle the situation of a significant change to a template record... 0. Backup your Gnucsh file just in case. 1. Forget about your existing template - disable it in fact. 2. Search for all created future txns matching the existing template. 3. Delete all 11 txns except for the very next occurrence. 4. Update the remaining next txn so it reflects what you want to see in your template. 5. Right click on the updated txn and select "Schedule" to schedule it and create a new template. 6. Update the new template record as necessary. 7. Run the "Since last run..." wizard to re-create your next 11 txns. 8. Double check the results. Job Done :-) I have a number of scheduled txns that change each year that I've tacked an "Effective 2019/07/01", "Effective 2020/09/17" etc onto the template name. As I create a new one I disable the old one, mind you I only create txns 60 days in advance not 12 months so no biggie for me :-) Or you could do the search for the future txns, export them to a spreadsheet, delete them in Gnucash, update in the spreadsheet and then re-import being careful to ensure you don't end up with duplicate txns because you forgot to delete the txns you exported as I once did. Cheers David H. On Thu, 18 Jan 2024 at 08:56, David G. Pickett <dgpick...@aol.com> wrote: > Yes, when editing the template and there are future transactions matching > the old template, I want it to ask me if I want to update the pre-scheduled > old matching future transactions to match the new template. > > On Wednesday, January 17, 2024 at 02:07:36 AM EST, 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. > > Regards David H. > > On Wed, 17 Jan 2024 at 10:43 am, Gyle McCollam <gmccol...@live.com> wrote: > > Instead of having 11 or 12 sx templates, why not have one that fires > monthly? > > > > Sent from Samsung Galaxy smartphone. > > > > -------- Original message -------- > From: "David G. Pickett via gnucash-user" <gnucash-user@gnucash.org> > Date: 1/16/24 6:18 PM (GMT-05:00) > To: Gnucash Users <gnucash-user@gnucash.org> > Subject: [GNC] Enhancement: Future sched txn update if updated template. > > I schedule my periodic transactions a year in advance, but with constant > inflation, often the amount goes up. It'd be nice to have a way to, by > interactive option after I update the template, have gnucash update the > already generated future transactions to match an updated template > transaction, so I do not need to update 11 or 12 more places. > _______________________________________________ > 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. > > _______________________________________________ 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.
