Hi,

Just before importing a CSV there is an option to "Make QIF File" which I like to use to have a QIF for archive purposes.

Unfortunately these QIFs are in the date format MM/DD/YYYY and I can't find anywhere to change that to DD/MM/YYYY which means I manually have to change each and every QIF.

Anyone has an idea where I can change that?

I'm using the latest stable for Windows although did a quick test yesterday on Debian 10 and get the same result.

Thanks.

Did you try to create your own QIF profile?
Menu -> Settings -> Configure KMyMoney -> Plugins -> QIF Exporter -> Configure button

There you can create new profile or edit existing "Default" profile. In Date tab choose desired ('%d/%m/%yyyy') format.

In export dialog choose modified 'QIF profile' next to 'Account to export'.

I did try that and have customized the QIF Profile accordingly. If I do an Export --> QIF it works and the date format is correct.

But not if I do Import --> CSV --> Make QIF File at the end of the dialog. It seems that it's not using the QIF Exporter Plugin to create the file cause any changes made in the Plugin have no effect to the export.

I'm wondering where the CSV Export Plugin gets the Date Format from.

I did not know that such a function existed at all and you're right, the date format is not taken from a profile but is hard-coded. The CSV importer does not make use any of the QIF exporter functionality, which somehow makes sense because it lives in another plugin.

Regular expressions could be a stopgap solution:

Find what:       D([0-9]{2,2})[/]([0-9]{2,2})[/]([0-9]{4,4})
Replace with:  D\2/\1/\3

the date format is not taken from a profile but is hard-coded

Awesome, thanks heaps for the link ipwizard. That explains it
Any chance this getting improved in the near future? Would I need to file a bug report?

Regular expressions could be a stopgap solution

Great idea Stephen, thanks for that. Did a quick test and works a treat. Will be doing it this way now for the time being.

mrbee wrote:

the date format is not taken from a profile but is hard-coded

Awesome, thanks heaps for the link ipwizard. That explains it
Any chance this getting improved in the near future? Would I need to file a bug report?

That would really help so that nobody forgets about it (and you get an information when it is done). Shouldn't be too hard to implement either

ipwizard wrote:That would really help so that nobody forgets about it (and you get an information when it is done). Shouldn't be too hard to implement either

Done. Appreciate your help. Cheers
https://bugs.kde.org/show_bug.cgi?id=452024