| Summary: | QFX file name not seen in file import dialog | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | Tom <whalento> |
| Component: | importer | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 5.1.3 | ||
| Target Milestone: | --- | ||
| Platform: | Mint (Ubuntu based) | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
screenshots of dialog box and file explorer
Screenshot from 2024-10-06 09-25-47.png Screenshot from 2024-10-06 09-21-09.png Screenshot from 2024-10-06 09-31-50.png Text Editor screenshot of the QFX file. |
||
I don't understand your problem. You say, that QFX files are not shown, but the provided screenshot shows one. What am I missing? Created attachment 174482 [details] Screenshot from 2024-10-06 09-25-47.png Sorry, grabbed the wrong screenshot. I found that by changing the Files of Type field on the QFX Import File Selection dialog box to "All Files" I could indeed see the qfx files. But the default dialog box opens with files types *.ofx *.qfx etc.... but none of those file types can be seen. See attached screenshot. So now that I can get past that small bug by using the display all file types, when I attempt to open the qfx file, I get the "incorrect format" error. See second screenshot. The qfx file was generated by my Quicken 2017 desktop software. So I thought I'd try the qif import. It doesn't do a good job delineating the fields. Basically just get a payee field with all data in it along with the date and amount fields. So I tried to create my own import template, but that "new" option is not showing. See third screenshot. I'm a retired IT guy and have done many translations for system conversions, but I'm kinda stuck here, and would really like to get off Quicken and on to kmymoney. I really appreciate your help Tom. If I need to open separate tickets for the above, just let me know. On 10/6/24 01:46, Thomas Baumgart wrote: > https://bugs.kde.org/show_bug.cgi?id=494127 > > Thomas Baumgart <tbaumgart@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > > --- Comment #1 from Thomas Baumgart <tbaumgart@kde.org> --- > I don't understand your problem. You say, that QFX files are not shown, but the > provided screenshot shows one. What am I missing? > Created attachment 174483 [details]
Screenshot from 2024-10-06 09-21-09.png
Created attachment 174484 [details]
Screenshot from 2024-10-06 09-31-50.png
I know you are on Mint (not Windows) but I wonder if the ofx/qfx filter might somehow be case sensitive, although it shouldn't. Try changing the extension from qfx to QFX to see if it makes any difference. In terms of "wrong file type" please post (or at least look at) the beginning of the qfx file, which should be plain ascii. There might be some header lines (possibly starting with something like "OFXHEADED:100") but within the first bunch of lines should be <OFX>. If it's some other type, there might have been a problem in creating/exporting it. QIF is known to be problematic, so I think both Thomas and I would prefer to get the OFX/QFX import working for you. No need to open other tickets unless we decide there is actually more than one bug present. Created attachment 174485 [details]
Text Editor screenshot of the QFX file.
You nailed it Jack. The file dialog box is case sensitive. I changed the file type to uppercase and the file dialog box displayed it! As for the format of the qfx file, it's bizarre. I used the Text Editor to generated the attached screenshot. I also looked at it on Windows notepad, same illegible format. Feels like I'm missing something... On the Artix Linux laptop I'm working on right now, the file open is case insensitive, so I wonder if there might be a relevant setting in Mint. Anyway, you at least know how to deal with that issue. That file is clearly binary, not text. What does "file filename" say about it? How did you create it? If that was quicken saying it was exporting a qfx file, it lied, unless perhaps it is compressed. (Ofx and Qfx are effectively the same, but the latter may have some Intuit defined differences that I've not seem matter.) I'm new to Linux, couldn't figure out directory path, etc to use the file command. But the Properties command confirmed it's type is binary. The QIF file on the other hand is clear text. DId some research and appears qxf is a proprietary quicken format, binary, of no use to me. So looks like I'm stuck with qif. Any way to create my own import template? As I mentioned above, the NEW option is not present on my qif import screen. Just Default. Just for future info, "file" is a linux command which tells you the type of the file you put as its argument. It should always be on your path. You should just open a command prompt (which will be bash running in a terminal) and tyep "cd Documents/finance" and then "file QDataSAV.qfx" However, that isn't likely to add any new information to the discussion. I'll have to research why you don't seem to have the option to create a new QIF profile. However, as far as some quick research shows, Quicken is supposed to export most account data as OFX (apparently not Investments) so are you sure you can't do this? QXF is almost OFX, with some Quicken specifics, but it is a plain text markup language, not binary. Please check again what quicken allows you to export. It may take more than one export to cover all your data, and some of it may need to be QIF or some format Excel can read (probably csv) but most should be able to be saved as OFX. Thanks for the info on file command. I was struggling with the directory structure, so you're explanation helped. As for Quicken exports, the only options on the export dialog are qfx and qif. But their help screens mentioned copy and paste. So I was able to copy and paste to a CSV file with headers. So maybe that's a good option for me to test. As you prob know, Quicken is notorious for making it easy to move your data to other programs, for obvious reasons. Such a pain. Hi, I've been able to successfully import using CSV. The import mapper mentions "account name in the first row", but I've not found any documentation on that. Is there a description of the csv import options? For account name, do I just need to put it in row 1, position 1? Can opening balance also be imported this way? We are coming more into the land of user support questions. This is a bug tracker. Please post these kind of questions on https://discuss.kde.org/tag/kmymoney . Thanks in advance. I suppose you're right Tom. Do I close this ticket, or do you? |
Created attachment 174427 [details] screenshots of dialog box and file explorer SUMMARY Linux Mint 22 Cimmaron STEPS TO REPRODUCE 1. copy file to be imported to folder "Finance" in Documents 2. Open File Import OFX in kmymoney 3. point to "Finance" in Documents OBSERVED RESULT copied file does not appear EXPECTED RESULT expect the file to appear in the dialog window ADDITIONAL INFORMATION Also cannot create a new import profile for QIF import. "New" option does not appear. So Can't find a way to import transactions from Quicken 2017 desktop version. Quicken only allow QFX and QIF exports.