Loading Profile...
Unable to parse a valid CSV file
Uploading the following CSV file fails with parsing error: http://www.nasdaq.com//asp/symbols.as...
I’m sad
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has a solution in progress.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Thanks for alerting us to this. In regards to this file, there are a couple things that I notice right away, and other things that are a bit more complicated. Someone here is working with this file to replicate everything, and then give a more detailed answer in the other post (http://getsatisfaction.com/gooddata/t... ).
Thanks for the detailed feedback!
I’m thankful
-
Inappropriate?I was able to replicate your problems. Let me share my revelations:
1) The CSV file uses the UNIX style line delimiter (^M). We choke on this delimiter for some reason. This was the real reason of the "cannot parse" error. I assume that once you have edited the file in Excel, the UNIX line delimiters got converted to WIndows style and the problem disappeared. I put this one in our Bugzilla.
2) The problem with non-numeric chars in number. We do not handle these characters well. Once we found them, we convert the whole value to NULL. We are planning to take care of such data cleansing in the January sprint so this should get resolved in Feb release. Today you really need to substitute these characters to empty string in your text editor (or sed).
3) The issue with "long values". I believe that we should have a silent protection against this type of issue. We should cut all long strings to first 255 characters. The protection did not work for some reason. Again, this is clearly a bug.
Thank you again for your help with our beta !
EMPLOYEE
EMPLOYEE
