Hello,
I've used other finance programs and for "split transactions" they just output 
each account per row, so I think all parts of a transaction should have its own 
row. It means more transactions but it's predictable. 
I'd keep it to just the raw data as close as possible, no conversions or 
grouping etc. It adds complexity and it's something I can easily do in whatever 
tool I'm exporting to. However, that's just considering what I want to use it 
for. 
Thanks,Alex






On Sat, Aug 13, 2016 at 9:45 PM -0700, "Martin Blais" <[email protected]> wrote:










There are couple of issues. In particular, one needs to - duplicate the desired 
transaction-specific data for each row (perhaps that's okay)- if the balance is 
to be rendered, if this balance contains multiple currencies, somehow replicate 
the row data for each of these- if you want to calculate anything, you'll have 
to aggregate by currency- convert to cost or market value if necessary.So 
there's no straightforward general answer... depends what you're trying to do.
However, a basic table report can be produced with something like this:
  bean-query $L 'select date, flag, maxwidth(description, 64), account, number, 
currency'
In order to export, this would be great:
  bean-query -f csv $L 'select date, flag, maxwidth(description, 64), account, 
number, currency'
But I haven't implemented shell output to CSV yet.



On Sun, Aug 14, 2016 at 12:02 AM, Alex Johnstone <[email protected]> wrote:
Ah yes, now that I think about it, it's not as straight forward as I originally 
(didn't) think.
My intent was to get some of the data into a spreadsheet to do some 
forecasting, when a foreign account is likely to get low so I can start 
preparing a transfer. Plus general trending and charting of various categories 
to see what's been happening over time.
I feel like I may need to write a script to output data from beancount when it 
meets certain criteria for what I'm looking for.





-- 

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/60512c29-710e-4b55-9b47-c6ff44e9db1e%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.








-- 

You received this message because you are subscribed to a topic in the Google 
Groups "Beancount" group.

To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/beancount/V-f6JFhR6R0/unsubscribe.

To unsubscribe from this group and all its topics, 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/CAK21%2BhNaUMSF9asDnprQfZmEKdsUremTyMX7vBwTDDFkTr1SAQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.






-- 
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/23ADF5F8C7089991.D68696F3-E461-486C-B331-53F7C73022BA%40mail.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to