Re: Struggling to get my first importer working (using Red's Importers)

Yes, it does! Turns out I wasn't paying close enough attention to the terminal type. Using the VS Code Beancount extension, I have it set to start fava when opening my beancount file. That automated process uses a PowerShell terminal, not Command Prompt, and I was just using that window, instea

Re: Struggling to get my first importer working (using Red's Importers)

You’re welcome, and glad to hear! Found this if it helps. ​ On Saturday, September 21, 2024 at 8:06:20 AM UTC-7 Joshua Cabrera wrote: > Thank you so much! Everythi

Re: Struggling to get my first importer working (using Red's Importers)

Thank you so much! Everything seems to be working now, so I just have to tweak my.import and catch up on recording in my ledger. Once I'm caught up, I'll come back to automating the download and extract workflow. Regarding the encoding issue, my first guess was it's because I'm doing all this

Re: Struggling to get my first importer working (using Red's Importers)

Thanks for the file! I can’t tell whether it was an artifact of how the ofx file you attached got created or whether the original ofx file suffers from this problem, but your ofx file is encoded in UTF-16 even though the header claims it’s UTF-8. ofxparse fails because of this. Running this al

Re: Struggling to get my first importer working (using Red's Importers)

Thanks, Red. The file itself looks okay after another look. I tried the new line trick, but it didn't change the results. The simple parse threw the same unpacking value error on my ofx while working on the sample ofx. I'm sharing a sanitized version of my ofx (replaced account number, transac

Re: Struggling to get my first importer working (using Red's Importers)

This is uncommon, but typically because there was an issue downloading the ofx. Usually because of authentication problems. Have you examined the ofx to see if it’s valid? Try this to make it more readable: sed 's/>/>\n/g' xyz.ofx ​ You should see something like this on the top: 0 INFO

Re: Struggling to get my first importer working (using Red's Importers)

This is uncommon, but typically because there was an issue downloading the ofx. Usually because of authentication problems. Have you examined the ofx to see if it's valid? Try this to make it more readable: ``` sed 's/>/>\n/g' xyz.ofx ``` You should see something like this on the top: ```

Re: Struggling to get my first importer working (using Red's Importers)

So, I've got my .ofx file and am not worried about the download task anymore. That's the good news. The bad news is now I'm stuck on the import task. bean-extract my.import fidelity_1234_july2024.ofx Results ERROR:root:Importer beancount_reds_importers.importers.fidelity.Importer.identify() ra

Re: Struggling to get my first importer working (using Red's Importers)

Glad you got it working with ofxget. bean-download is just a wrapper around ofxget or whatever command you have to parallelize all your downloads. If you don’t have several accounts you’re using it with, it’s of limited use. The built in template for fidelity is here, and lets you store your

Re: Struggling to get my first importer working (using Red's Importers)

Quick update: Installed ofxget and manage to get my ofxget.cfg updated using ofxget acctinfo. Not sure if this required for bean-download. Also downloaded a .ofx file using: ofxget stmt fidelity > c:\users\joshd\fidelity.ofx Struggling to my download.cfg and bean-download download working - kee

Re: Struggling to get my first importer working (using Red's Importers)

My reason for using .csv over .ofx is simply familiarity and ease of starting up. I have no experience with ofx and thought the learning curve would be much steeper, and I already feel like I'm drowning a bit as a layperson. I know it may seem like that, especially given ofx is not a human re

Re: Struggling to get my first importer working (using Red's Importers)

My reason for using .csv over .ofx is simply familiarity and ease of starting up. I have no experience with ofx and thought the learning curve would be much steeper, and I already feel like I'm drowning a bit as a layperson. I'll look into the csvreader changes you mentioned to try making a re

Re: Struggling to get my first importer working (using Red's Importers)

Now I find myself stuck. All I get ";; -*- mode: beancount -*-". I've inserted some print functions inside the methods, and it seems like it's not reaching prepare_raw_columns(). You’re doing nothing wrong, BTW. CSV parsing changed csvreader a while ago, and wasn’t fixed in this importer sin

Re: Struggling to get my first importer working (using Red's Importers)

Agree, I ran the run_tests.sh in that importer and ran into the same issues. Sorry you ran into these. The problem seems to be that this importer doesn't use a standard pytest setup, and the unit tests therefore haven't run in a long while, while several things changed underneath it. It also se