CSV import problem with some banks
Bug #400350 reported by
Gavin Chappell
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
wxBanker |
Incomplete
|
Medium
|
Unassigned |
Bug Description
My bank in the UK (Alliance and Leicester, for what it's worth) uses the following format for CSV exports meaning that the CSV import feature doesn't work correctly when it hits a debit transaction. Works fine for putting money into the account but taking money out crashes the importer as there's no way of specifying a separate field for credit and debit.
Date,Descriptio
Also in the CSV importer, can the profiles be automatically loaded when you select one, rather than requiring a (unnecessary IMO) click on the Load button?
Changed in wxbanker: | |
milestone: | none → future |
Changed in wxbanker: | |
milestone: | 0.9 → future |
To post a comment you must log in.
Thanks, that is true indeed! I have a blueprint for improving the CSV import at https:/ /blueprints. launchpad. net/wxbanker/ +spec/csv- import- 2.0, I will link it. If you have a minute please read it over and give any comments on it; I think it should cover these issues.
If you are feeling adventurous and are at all familiar with coding (python), feel free to branch lp:wxbanker/0.5 and start hacking :) The relevant files are csvimporter.py (http:// bazaar. launchpad. net/~mrooney/ wxbanker/ wxbanker- olv/annotate/ head%3A/ csvimporter. py) and csvimportframe.py (http:// bazaar. launchpad. net/~mrooney/ wxbanker/ wxbanker- olv/annotate/ head%3A/ csvimportframe. py)