Bug 432397

Summary:	kmymoney could simplify importing CSV files
Product:	[Applications] kmymoney	Reporter:	Matthew Schultz <mattsch>
Component:	importer	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	REPORTED ---
Severity:	wishlist	CC:	KDE
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Matthew Schultz 2021-02-01 20:20:32 UTC

Due to bug 428146, I've been exporting a CSV file from my bank's website and importing it through the CSV import option in kmymoney. There are a way too many steps to have to follow for each import.  It would be nice if this could be sped up.  I have been choosing the same options every time with perhaps sometimes a change in filename although most times I just save over the same file I exported from my bank's website from the last time.  I know I can check "skip setup" but that only reduces 8 steps into 4 steps.  I'd like at most two steps:  one to select the account to import to and the other to select the file.  Maybe it could even remember the name of the last file I imported and skip selecting the file so I just say which account I want to import to.  At any rate, it would be a lot nicer to have a faster import since there's no longer support for downloading transactions through kmymoney anymore through my bank.

Comment 1 Brendan 2021-02-01 22:12:59 UTC

I have a few accounts that no longer provide direct connect access so I used the CSV imported today for the first time in a while. I agree that it's a lot more work than it could be.

It would be nice if it worked like mapping an account for direct connect. When I map an account there are 2 options, kbanking and ofximporter. What if there was a third option for localcsvimporter. In there you would define the file path and name for the CSV file, the CSV setup that you have defined and anything else that is needed. Then all I have to do is update the CSV files on my system and when I run "Update all accounts" the CSVs are also imported or I can just update one account mapped to a CSV file.

Now that I think of it, this could also be used for locally stored OFX files. Rather than manually selecting the file each time, why not add a mapping option to a local path a file name? This could be called localoxfimporter.

Then all I have to do is download CSV and OFX files and save them to the same file, KMM does the rest. This seems like mostly an interface problem since the code to import CSV files and OFX files is already done.

Clearly this all belongs on the wishlist.