You don't even need to do this: just look at the date of the last transaction in the accounts that are affected by the automatic transaction and have the code avoid generating automated transactions before that date.
On Tue, Nov 18, 2014 at 12:59 PM, ELI <[email protected]> wrote: > I was thinking this could be achieved with a tag. Each automatic > transactions could be generated with a deterministic tag (i.e. the > automatic transactions name/id + scheduled transaction date). Then, to > replace it with a manual transaction, the user could copy the automatic > transaction and tweak necessary fields, or the user could just copy the tag > and apply it to a manual transaction. > > - Harpreet "Eli" Sangha > > On Tue, Nov 18, 2014 at 9:51 AM, Simon Michael <[email protected]> wrote: > >> I like where you're going with this.. I was thinking some similar >> thoughts. Eg an automated transaction is automatically skipped in a period >> where a similar manual transaction is found. I was thinking the description >> field would be the easiest way link these, since date and amount might vary >> slightly. >> >> >> -- >> >> --- You received this message because you are subscribed to the Google >> Groups "Ledger" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > > --- > You received this message because you are subscribed to the Google Groups > "Ledger" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
