Report system legacy

Alex Aycinena alex.aycinena at
Thu Jun 27 13:07:13 EDT 2013

> ---------- Forwarded message ----------
> From: John Ralls <jralls at>
> To: Derek Atkins <warlord at MIT.EDU>
> Cc: gnucash-devel at
> Date: Thu, 27 Jun 2013 07:18:14 -0700
> Subject: Re: Report system legacy
> On Jun 27, 2013, at 7:04 AM, Derek Atkins <warlord at MIT.EDU> wrote:
> > Geert Janssens <janssens-geert at> writes:
> >
> >>> HOWEVER, I do think that we should only have a single saved report of
> >>> the same name. I.e., if we save a Balance Sheet report it goes into
> >>> Custom/Balance Sheet which is fine. But if you *resave* it, IMHO it
> >>> should overwrite the previously saved Custom report of the same name.
> >>>
> >>
> >> That may not be the user's real intention. Instead the user may want to
> >> generate a second report based on the same base report, but using
> different
> >> settings. So I think automatically overwriting the previously saved
> report may
> >> result in user frustration. At the very least we should ask the user
> what she
> >> wants to do.
> >
> > I'm not sure..  Perhaps the best way to do it would be to do it similar
> > to other systems and prompt the user: "Another saved report already
> > exists with the name XXX.  Overwrite?  [Cancel] [OK]" This would prompt
> > them to change the name if they really want two reports with the same
> > name.
> Alternatively, do what Macs do: append ' (n)' to the name part of the
> filename,
> where n is a positive integer incremented as necessary.
> Regards,
> John Ralls
Another idea (without consideration about how hard it would be to
implement) is to store the date/time of creation as a separate attribute of
each custom report and display this along side (or perhaps appended to) the
name, wherever a selection is made (that is to say, if there is only one
field where a selection is made, concatenate the name/date/time just for
the purposes of selection display). That way, if the user wanted to keep
the same name on multiple reports, there would be a way of distinguishing
between the duplicates.



More information about the gnucash-devel mailing list