Metadata on the open directive might be useful? for example: 2017-03-01 open *Assets:Credits:CLIENT* address: "" telephone: "" contact:""
and build the invoices with a python script. I use this approach with one of my importers, my importers.config builds a list of all open directives with a given metadata (unique ID in the bill-autopay-system from), and passes this list to an importer that parses this ID. On Wednesday, April 26, 2017 at 5:07:14 PM UTC+2, [email protected] wrote: > > Hello All, > > Is there a way to query directives which are not transactions? > Currently I'm seeing this: > > beancount> select * where type != "transaction" > > (empty) > > beancount> > > > > The problem I'm trying to solve is invoice generation: want to store > client-specific metadata (e.g.: address) in the ledger somewhere; then > query them and have the results be the various fields of the generated > invoice. > > An example might be: > > 2017-03-01 note *Assets:Credits:CLIENT* "Via Lungolago 13, > CH-6900 Lugano" #address > > And an example query might be: > > SELECT last(narration) FROM (type = "note") AND ("address" in tags) WHERE > account = "*Assets:Credits:CLIENT*" > ... assuming that a note's text field is referred to as "narration". > > This would have the advantage of being able to declare new addresses if > the client moves. > The #address tag is so that other notes may exist without breaking this > query. > > > > I'm not sure if this is the way this problem should be solved, maybe a > different approach is best? > > Thank you very much, > > Sirio > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/5fde9f42-b83a-4dc7-9b07-bb73ec0eda7f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
