F2O Working nicely with the new Fidelity CSV file formats.

[Cal Learner]

F2O_beta21.zip uploaded.

The latest change addresses some transactions that would be missed for import because the History CSV lacked symbols for some transactions.

The newer versions should still work with the older CSV format if they were to revert that.

[danba...@gmail.com]

Thanks for constantly keeping this updated Cal.

 

Do I understand from a previous recent post you made that I should set my <date> to the date+1 of my last successful download with the old format? For me, my last download 2026-06-26, prior to Fidelity making any changes, so I’d use 20260627. I haven’t downloaded anything since then as you discovered the issues and started making updates.

 

IGNORE_BEFORE_YYYYMMDD="<date>"

 

Cheers,

Dan

--
You received this message because you are subscribed to the Google Groups "Microsoft Money" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microsoft-mon...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/31a42cb4-eeb5-4961-9d64-842fc46796bfn%40googlegroups.com.

[Cal Learner]

Look at how the transactions in the register are dated. So if you downloaded 6-26, it may be that you only have 6-25 and before already in. But if you have the 2026-06-26 transactions. then do

IGNORE_BEFORE_YYYYMMDD="20260627"

There can be a time where you have some transactions downloaded for a day, and you might decide to do a day of overlap on purpose, knowing that you must be alert to deleting any old duplicate, or Voiding any new duplicate.

[Cal Learner]

ALERT: they changed my "Accounts_History - 2026-07-10*.csv" back to the OLD format!!  What timing! There had been some complaint about having changed, and they actually put it back.

So I will need to 

1. Restore my latest backup  --  in my case 07/08/2026  08:07 PM

2. File->RestoreFromABackupFile.

3. Note that I had transactions dated 6/8/2026 in my registers

4. set  IGNORE_BEFORE_YYYYMMDD="20260709" in my F2O_cfg.py file.

5. Re-run F2O, which in my case is to run F2OPS.bat.