CSV Import

[Steve Isenberg]

I removed the carriage return from the end of the line and left only the line feed. That did not help. Also, tried adding an extra column before the line feed and that did not help either. Thought your suggestion of the CR and LF in the windows file might be a solution but removing the CR did not help.
Unless there is another trick or work around I'm inclined to say the Windows CSV import is non-functional.

It was suggested I try using the Excel macro to convert to QIF. Once I get caught up I will see if that works. Also, once caught up I will help test the split-transaction import, but need to keep moving.
Thanks


      From: Geert Janssens <geert.gnucash at kobaltwit.be>
 To: Steve Isenberg <brrg58 at yahoo.com>; "gnucash-user at gnucash.org" <gnucash-user at gnucash.org> 
 Sent: Sunday, April 2, 2017 2:06 AM
 Subject: Re: CSV Import
   
The date format was just a distraction indeed. Silly of me to not recognise the standard US format...

The only difference between our setups is the OS. So maybe the line endings are tripping up the importer. Try adding one more empty column which you don't import.

Regards,
Geert 

Steve Isenberg <brrg58 at yahoo.com> schreef op 2 april 2017 02:50:54 CEST:
No way, there is no way the CSV import works!

To start I removed the header row as it wasn't really needed.

The original date format was the typical US, m/d/yyyy. I changed it to d-m-yyyy, replacing the forward slash with a hyphen. It failed.

I changed the date to yyyy-m-d, and it failed.

This is the test data that I tried to import:

    2017-2-1,Pamela H,18
    2017-2-1,John L,18

Preview Settings (screen)
Start import on row 1 and stop on row 2
Encoding: Unicode (UTF-8)
Data type: separated
Separators: comma
Date Format: y-m-d
Currency Format: locale
Step over Account Page if Setup: checked

Click the Forward button

Account Selection (screen)

ERROR: 
There are problems with the import settings!
The date format could be wrong or there are not enough columns set...

Every time, it fails at the same place and with the same message, every-single-time.

I am running Windows 7.

I don't want to do data entry as I have data from multiple sources that I want to import. 

What columns are supposed to be in the CSV file?
What are the formats of each column?
I need a work around or a fix to move forward. 
Thanks
      From: Geert Janssens <geert.gnucash at kobaltwit.be>
 To: Steve Isenberg <brrg58 at yahoo.com> 
Cc: "gnucash-user at gnucash.org" <gnucash-user at gnucash.org>
 Sent: Saturday, April 1, 2017 4:55 AM
 Subject: Re: CSV Import
  
On vrijdag 31 maart 2017 22:24:20 CEST Steve Isenberg wrote:
> If the current CSV import has a simple use case then why does it always
> error and never import? The error screen is no help whatsoever in
> determining the error.
> I created a CSV with columns as displayed on the transaction input screen.
> Does not work. I stripped the CSV down to the columns described below. Does
> not work. What columns are supposed to be in the CSV file?
> What are the formats of each column?
> This is an example of the data based on the columns mentioned below:
> Date,Description,Income
> 1/1/2017,Garri Ann Hearn,18
> 1/1/2017,Garri Ann Hearn,11
> 1/1/2017,Pamela Healy,18
> 1/3/2017,Robert Marten,100
> 1/4/2017,john landi,7
> The CSV import fails consistently without any real clue as to the problem.
> How is this data supposed to be formatted? Searching the archives is not
> helpful. There are too many unrelated results in the archive. This is a
> straight-forward problem and if the CSV is simple then it should not be
> difficult to figure this out. Appreciate the help.Steve
> 

Hi Steve,

I have just tried your sample data and got to the last page of the importer 
with no issues (the page where you can assign accounts to each of the 
transactions). My first attempt failed because I didn't select the proper date 
format. Setting it to "d-m-y" got me through with no problems.

At which point does it fail for you and how ?

Regards,

Geert


   

Sent from my smartphone. Please excuse my brevity.