[GNC-dev] GnuCash 3 on Linux
adrien.monteleone at lusfiber.net
Wed Mar 6 13:22:44 EST 2019
I’ll hazard a quick guess that everything not in the accounts tab is non-book specific.
At the very least, the display and general tabs are not.
How you want figures to be displayed, which sets of figures, which periods...
Content settings may be tied to the book, but formatting settings are likely to be the most likely to be used cross-book. I can certainly see someone wanting all of their reports looking the same.
> On Mar 6, 2019, at 9:18 AM, Derek Atkins <derek at ihtfp.com> wrote:
> Coming at this late...
> Geert Janssens <geert.gnucash at kobaltwit.be> writes:
>> For starters the user preference is an all or nothing thing, either all
>> reports are in a book or in a common location. That's not very fine-grained.
>> Perhaps you consider some reports common and some reports book-specific. This
>> could be solved by making it a per report option of course.
> I can picture very few cases where a configured report is not tied to
> the book. If it contains references to *ANY* accounts, then it is, by
> definition, book-specific and should live with the data. This is, IMHO,
> most reports.
>> And yet another issue: reports are only suitable for multiple books if these
>> books have the exact same base as required per report. An example to clarify
> The only time all saved-reports are useful across books is if the books
> are derived from the same base. I.e., you copy, or save-as.
> If the reports are stored in the book data itself then you get this for
>> So my conclusion is that report configurations are essentially book specific
>> and should be treated as such to avoid unexpected accounting mistakes.
>> On the other hand I understand it takes time to carefully configure
>> reports to your preference and there's a wish to reuse this effort
>> across books.
> Perhaps we need an "export report configuration" that can extract the
> non-book-specific settings?
More information about the gnucash-devel