Alert: Fidelity PocketSense Users: Do not do GetData today.

[Cal Learner]

Keep a copy of your current Fidelity*.ofx files that are in the XFR folder before proceeding.

Those previously successful OFX files can make creating the database that F2O uses much easier. The database can be prepared from scratch, but that easy starting point is better.

GetData deletes existing *.OFX files from the XFR folder before trying to fetch new ones. So if Fideliy server stops working for you, as it did for me today, you could lose the latest successful Fidelity OFX files.  Using Setup.py to run test is safe. It will try to get new OFX files for an account without deleting the existing OFX files.

I would like to hope this is a temporary glitch, but we knew it was a matter of time.

https://microsoftmoneyoffline.wordpress.com/2024/02/03/cals-fidelity-specific-csv-to-ofx-converter/

[Cal Learner]

For those not sure they want to use F2O, at least save the OFX files you have to potentially use later.

F2O comments:

I am looking at F2O and considering some simplified or target documentation.  I see 3 kinds of F2O users....

1. Those who have at least one set of old OFX files to gather info from. (that is where the existing notes are mostly aimed)

2. Those who will want to create a database CSV that will let Money recognize past investments.

3. Those who are content to let Money generate a pseudo-CUSIP, and for each investment, identify that this investment already exists under a different name.

Which group would you be, and do you see group 2 or group 3 as who I should concentrate on next?

If continuing to use PocketSense for other FIs, having a batch file put the resulting OFX files into the PocketSense Imports folder would be good after the initial setup, experimenting, and testing is done.

It has been months since I last worked on F2O, in anticipation of the Fidelity OFX/QFX server being disabled. So I have to re-learn too.

Note that F2O is written for Python 2.7 like PocketSense. I expect to get that to work with Python 3. Different version of F2O or be able to use either interchangeably.

I expect to put a new download file up today or tomorrow.  If you experiment before then, please add this two-line file to F2O folder:

=============begin F2O_cfg.py===================

IGNORE_BEFORE_YYYYMMDD="20251210"
DEBUG=0

================end  F2O_cfg.py===========================

My last successfully downloaded transactions were from Dec 9. This will avoid duplicates. F2O generates unique FITID entries, but they will not be the same as what would have been generated. If your latest are earlier, adjust that string.