I do the same. I have general configurations saved, but anything
particular to that solitary instance of the report, I do not save as
part of the configuration. Those will be one-offs so no need to save
them as a config, just run and if I want, save as a PDF.
Regards,
Adrien
On 2/13/23 8:18 AM, Michael or Penny Novack wrote:
However, there IS a different approach possible.
I do not consider the SAME report except run for a different
date/period to be a different "configuration". I consider
"configuration" to refer to things like display options, nesting levels,
what accounts to include/exclude, etc. But not dates.
So how do I handle the reality that I have many P&L reports, many
Balance Sheet reports, etc. run for different dates?
I create directories (file folders) to hold them with suitable names
(like Balance Sheets) and then after running the report in gnucash I
export it to this folder using a suitable file name that clearly
identifies it. Thus I might name the the file which is a Balance Sheet
run for the effective date of Jan 31 "BalanceSheet20230131"
Mind, I've been using gnucash since 2007, so if saving within gnucash
data. It would be a ridiculous amount of clutter within gnucash data if
I kept them all there. The fact that I knew to do this from the start
(when there were just a few) is because I was a freshly retired pro.
Avoid future problems.
_______________________________________________
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.
