Re: Beanquery - Return the other account involved in a transaction

There is no guarantee there will be only two accounts represented in a transaction. So this may result in multiple "other account" entries returned. Given your inputs above the query and result is possible with beanquery : $ bean-query ./test.beancount 'select date, narration, account, oth

Re: Beanquery - Return the other account involved in a transaction

Thank you Matthew! I realize now that it's a supported option, I just couldn't find it in the documentation . On Sunday, November 13, 2022 at 5:07:31 AM UTC-8 matthew...@gmail.com wrote: > There is no guarantee there will be only

Re: transfer_lots Plugin "locks" lots

I looked through some threats I could find, but I didn't find any (automatic) solution to this problem, actually. - the plugin posted in my initial posting doesn't work - https://github.com/hoostus/beancount-asset-transfer-plugin doesn't work (only supports LIFO and has errors) I guess, I found

Re: transfer_lots Plugin "locks" lots

I agree with your analysis. Honestly the easiest way before+if this is officially supported may be to hack the beancount source and so it rewrites the lots before booking. Start here: https://github.com/beancount/beancount/blob/3ec62d4d8e68f352156eec6c7068b8aee8fc65f1/beancount/loader.py#L531 and a

Bean report without "ammending" the txns?

Hi, is it possible to use bean-report … print without "amending" the original txns? By amending I mean: - bean-report fills empty reductions of lots (Assets:XY -1YZ {} ==> Assets:XY -1YZ {3 USD, 2022-01-01}), which I don't want at this point. - bean-report removes txns that contain errors Cur