homebank cannot import its own CSV exports

[CW Verhey]

homebank 5.5.3

OS: MacOS 10.15.17, also reported by someone on Windows (same HB version, don't know their OS version)

When exporting CSV from an account (doubleclick account > Account > Export CSV...), the resulting CSV contains a superfluous column named 'c' which prevents Homebank from accepting its own export for later import.

Example:

homebank export:
date;paymode;info;payee;memo;amount;c;category;tags
12/01/2019;8;IDB;bakery [NL91RABO0135497523];576416 0000002776064170 thank you come again;-3,35;;;

should be (IMO):
date;paymode;info;payee;memo;amount;category;tags
12/01/2019;8;IDB;bakery [NL91RABO0135497523];576416 0000002776064170 thank you come again;-3,35;;

[Maxime DOYEN (mdoyen)]

just curious what is your use case, to export and then import again ?

yes, the documentation specify this: http://homebank.free.fr/help/misc-csvformat.html
the addition of 'c' column was required in #1847907 since 5.4 release.

note for me:
- could be a new checkbox unchecked by default
- add message warning if it is checked, like it should be detail split line

[CW Verhey (cwverhey)]

Hi Maxime,

There is no immediate use case; another HB user was asking for my help to understand the import CSV format and we came across this inconsistency coincidentally.

Apologies for missing that this is intentional behavior. I hadn't noticed this 'new' documentation yet. I maintain a CSV conversion tool for a few Dutch banks, but last time I went through the documentation must have been around 2011 (http://caspar.verhey.net/ing-homebank/). Good to see the documentation on the CSV import/export is more extensive now; I'll update my GitHub readme to point to them.

For ease of use, it would be nice if the CSV importer would simply ignore (with or without warning) any extra columns, and if the order of the columns wouldn't matter. Though I see Homebank also accepts CSVs without column name headers, so it might be harder to implement than it is worth. So please don't consider this as a formal feature request, just a small idea.

Again, apologies for missing this as intentional behavior; for me this ticket can be closed.

Kind regards, Caspar

[Maxime DOYEN (mdoyen)]

As I did had some other people pointing this I will do what I was thinking:
- add a new checkbox unchecked by default to add the status colunm
- add message warning if it is checked, like it should be detail split line and which is not

so that by default that file will remains as it was previous #1847907 add of status column
and if some option are checked, the user will know that it will not be the case