Interesting, thanks for sharing. This is similar to what I ended up doing although with fava it's a little clunky since you can't extract in the UI with the account set to an empty string. It's minor but seems to work perfectly fine for bean-extract.
Thanks again! On Monday, August 29, 2022 at 12:42:00 AM UTC-7 Patrick Ruckstuhl wrote: > Hi Allan, > > I have actually lots and lots of importers which don't map to a file per > se. For all of them I use actually the configuration file for the importer > (e.g. with credentials in it) to trigger it. That works very well for me. > > It's also not a problem to return entries with different accounts than the > account you indicate on the importer (e.g. I import from some api where > there are different accounts behind it). > > > If you want some examples, you can find them here: > https://github.com/tarioch/beancounttools > > > Regards, > > Patrick > > > On 28.08.2022 22:56, Allan Calix wrote: > > > - No natural account name to map to (i.e. `file_account`). Because the > stream of transaction relates to multiple beancount accounts, filing > doesn't make much sense in this context. This is minor as the file could > be > deleted after import, but is a bizarre flow when used in fava. > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/beancount/9ddd6448-1284-48fc-a494-fa00ea1c32b7n%40googlegroups.com.
