On 2026-10-09 16:06, Adrien Monteleone wrote:
Sorry I'm late to this party...
You're the only person that arrived and brought a bottle :)
I've played around with tags in the past, but don't presently use
them, though I likely will start doing so in the near future.
I mostly rely on the following that allows me to get most of what I
need from reports:
1. Description is simply Payee/Payor, great for reporting on sources
or destinations of funds
Description is included in the tag_table so you can pivot on them, won't
be of use for that purpose for most people.
2. Notes contain things like general purpose for the transaction. I
likely have a few transactions where I used a # or @ symbol preceding
a commonly used term from back when I was doing testing. I think both
would be useful for their own context: # would designate a subject
matter such as #vacation, while @ would designate a place such as
@jamaica. I might well also use : for a time period such as
:june-2025. One might ask, "why not just use the report's date ranges
instead?" but there are use cases (like business trips) which might
cross period boundaries and you want to refer to it by a particular
instance which is date/time based. I would guess multiple tags would
either be separated by a space, or comma.
I haven't bothered with Transaction Notes so far because they live in
the slots table along with a jumble of other stuff. I'll probably dig
them out over the weekend. How you actually tag things is immaterial so
long as you can get them to match a Regular Expression.
3. Memos for extensive detail on every line item if possible. I rarely
have empty Memos. This is probably my most used field to filter for a
report.
I don't use the Action field save for the Business Features
automatically indicating 'Payment' where appropriate, but it would be
nifty to be able to filter on that field so tags could be employed
there and be noticeable at a glance. (I use Transaction Journal view
exclusively, with Double-Line mode) Since my Memos almost all have
something in them already, Action would be an easier place to spot
tags and be a bit cleaner to read.
Memo and Action field are both checked for tags.
From what I recall of previous threads and my own testing, the most
requested report use would be for the Income Statement to use
filtering. I've played around with trying to craft a multi-column
report with the Transaction Report as a work-around, but I wasn't able
at the time to achieve something similar. This leaves having to run
two Transaction Reports, one for Revenue, another for Expenses, and
then exporting both to a spreadsheet for a combined presentation with
the usual bottom-line math.
The full account field (e.g. Assets:Bank:ABC:Deposit) is exposed so it
can be pivoted / filtered on in your spreadsheet, i.e. limit the pivot
to just Income and Expense accounts for an Income statement.
Thanks for your message, Adrien, at first glance the only thing I've
left out are tx notes.
Wm
_______________________________________________
gnucash-user mailing list
[email protected]
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.
