Help needed with changing scheduled transactions end dates please.
Christina Martin
christina at airgeadstudio.net
Wed Jul 16 21:49:39 EDT 2014
On 17/07/14 02:00, gnucash-user-request at gnucash.org wrote:
> Message: 13
> Date: Wed, 16 Jul 2014 15:00:28 +0100
> From: Wm<wm+gnc at tarrcity.demon.co.uk>
> To:gnucash-user at gnucash.org
> Subject: Re: Help needed with changing scheduled transactions end
> dates please.
> Message-ID:<LdhR26T8VoxTFwf1 at tarrcity.demon.co.uk>
> Content-Type: text/plain;charset=us-ascii
>
> Wed, 16 Jul 2014 13:47:13
> <5067511.YrzqpZK3kM at calufrax.nottingham.standbyevents.co.uk> Maf. King
> <maf at chilwell.net>
>
>
>> >I think you've missed the point of the OP.
> Possibly
>
>> >The way I read it, Christina has
>> >decided to change her use of GC to be continuous, as you suggest. However,
>> >she is having trouble changing her SXes from having an end date to running
>> >forever... your point about not creating duplicate transactions might be worth
>> >noting, though.
Hi Wm and Maf, thank you for trying to help me.
Maf, you are correct. I decided to change the existing GC file to be
continuous. I realised in the last financial year that I wasn't
handling the files correctly. Rather than starting a new file for the
new financial year, I wanted to keep going with my existing file. In
order to do that, I needed to edit my SX to be never ending (instead of
the arbitrary 31 July that I had put on them when I started the file)
and this is where the problem arose. Not that GC thought they'd already
been created, but instead that I could not change them from a set end
date to be never ending.
I have checked and I do not have duplicated entries.
> An SX looks something like this
> ===
> <gnc:schedxaction version="2.0.0">
> <sx:id type="guid">xxxxxxxxxxxxxxxxxx</sx:id>
> <sx:name>xxx</sx:name>
> <sx:enabled>y</sx:enabled>
> <sx:autoCreate>y</sx:autoCreate>
> <sx:autoCreateNotify>n</sx:autoCreateNotify>
> <sx:advanceCreateDays>45</sx:advanceCreateDays>
> <sx:advanceRemindDays>0</sx:advanceRemindDays>
> <sx:instanceCount>38</sx:instanceCount>
> <sx:start>
> <gdate>2010-09-09</gdate>
> </sx:start>
> <sx:last>
> <gdate>2014-08-21</gdate>
> </sx:last>
> <sx:templ-acct type="guid">xxxxxxxxxxxxxxxxxxxxxx</sx:templ-acct>
> <sx:schedule>
> <gnc:recurrence version="1.0.0">
> <recurrence:mult>2</recurrence:mult>
> <recurrence:period_type>week</recurrence:period_type>
> <recurrence:start>
> <gdate>2010-09-09</gdate>
> </recurrence:start>
> </gnc:recurrence>
> </sx:schedule>
> </gnc:schedxaction>
> ===
>
>> >Christina: Sorry, no ideas here....
> C either has or doesn't have some dates on the scheduled transactions in
> her current file. My thought is that she had created the transactions
> in the old file so the new file is "thinking" "we've already created the
> transactions so we won't do it again" because of the last (2014-08-21 in
> the example above).
>
> Make sense?
>
> If I'm right-ish she needs to play with the Scheduled Transactions /
> Overview options OR play with Edit / Prefs / Scheduled Transactions so
> it starts again
>
> -- Wm...
Wm, I've looked in Edit > Preferences > Scheduled Transactions, but only
have options of when to run the "Last Run" dialogue, whether to
auto-create new transactions and how far in advance for auto-create and
reminders. The Scheduled Transactions / Overview tab is where I was
trying to change the date and where the problem occurred.
I decided to do some more playing with it, as I had to pay some personal
bills last night, and ended up spending an hour on the SX. I tried
creating new SX from an existing TX but GC recognised that I already had
the SX set up, so instead I had to go through and delete each SX
individually, then recreate it from the existing TX. I've now done that
for all the SX in my personal accounts. If need be, I'll do it that way
for my business accounts, but would prefer not to have to. It *should*
just allow the change.
It seems like the file is locked from saving an edit to that particular
field, which is why I then tried changing permissions, unsuccessfully as
it turned out.
Regards,
Christina
More information about the gnucash-user
mailing list