lj, I'm Pretty sure you're correct on that. I have tried previously to update Scheduled Txns so I could delete incorrect ones and recreate them from a certain date but without success. I've never found anything to reset the last occurred date recorded in Gnucash and invariably ended up manually creating a new Scheduled Txn. I have just tried right clicking on a past transaction that was created by a Scheduled Txn template and clicking Schedule on the context menu that pops up. This created a duplicate Scheduled Txn with a last occurred date of never which I was able to edit and get triggered by using the "Since Last Run..." menu item so you can probably replace a bad Scheduled Txn this way.
Cheers David H. On Tue, 16 Feb 2021 at 11:23, lj <lj...@pobox.com> wrote: > I am pretty sure that does NOT work. You can change the start date for a > scheduled transaction forward, or backwards, or change the transaction to > non-repeating and then back to repeating... and the "last triggered" date > will > not change. Someone correct me if I'm wrong but I think editing the file > is > the only way to set the last triggered date to an earlier date (or to > remove it). > > > David Carlson wrote: > > I think it may be possible to set the start date for an existing > scheduled > > transaction to an arbitrary date in the past to effectively reset the > clock > > on that scheduled transaction. However, I do not have a test file handy > or > > the time to pursue that theory myself. > > > > Alternatively, one could duplicate a previously created transaction, then > > memorize that transaction. If the original scheduled transaction > contained > > formulas, the newly created scheduled transaction would have to be edited > > to insert those formulas. While formulas can be inserted into existing > > transactions, they get evaluated instantly when the edit is committed, so > > they must be saved as scheduled transactions to remain as formulas. > > > > One would have to remember to give the new scheduled transaction a > > distinctive name to be easily found in the list of scheduled > transactions, > > since it will likely be named similarly to other existing transactions. > > > > > > > > On Sun, Feb 14, 2021 at 8:46 PM lj <lj...@pobox.com> wrote: > > > >> bdp3 wrote: > >>> But I still don't understand HOW to rerun the SX using a date in the > >> past... My SX has many lines and deleting/re-writing it would be a > hassle. > >>> > Questions: > >>> > How can the Scheduled be re-run for prior periods? > >> > >> The only way to do that is by editing your Gnucash data file with a text > >> editor. Not recommended unless you are confident, keep backups, etc. > >> Basically > >> you close Gnucash, uncompress (gunzip) the data file, and open it in > your > >> text > >> editor. Look for your scheduled transaction by name (<sx:name>...), and > >> change > >> the date in the sx:last tag. Save the file, recompress it with gzip, and > >> reopen it in Gnucash. > >> > >> I've always thought it would be a neat feature to add: Have gnucash > reset > >> the > >> last triggered date for a scheduled transaction if you change the start > >> date > >> (or something like that). No UI changes needed. It would provide a way > to > >> fix > >> problems like this without affecting much else. > >> > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > ----- > 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 If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
