Page tree
Skip to end of metadata
Go to start of metadata

In your GoodData trial, you can upload a Comma Separated Values (CSV) file using our sample uploader to quickly explore GoodData’s reporting and visualization capabilities. Follow the format guidelines below to successfully upload a CSV file. If you have trouble with your upload, please email and attach your CSV file.

General Requirements and Tips

Creating a CSV File

  • You can easily create a CSV file by opening a file in a spreadsheet program, such as Microsoft® Excel®, selecting “Save As,” and setting the file format to “comma separated values .csv”

  • You can also export reports from Salesforce, Marketo, and other systems directly to CSV format.

Formatting Tips

  • Ensure your file has a header row at the top containing the name of each column
  • All rows in a column should be formatted consistently
  • Each field in a row should contain a value – avoid blank cells
  • Each record, including the header, must contain the same number of fields.
  • Commas, semicolons, pipes or other standard delimiters must be used to separate all fields.
  • The last field in the row should not contain a comma or other field delimiter
  • There should be no empty rows at the end of the file

Number Formatting

  • Use the plain #######.## format for numbers – remove thousand separator commas (,) currency symbols ($), percentage signs (%), and scientific notation (12E3) .

Dates Formatting

  • Ensure your date values are between the years 1900 and 2050 – GoodData’s supported range.
  • Make sure your dates follow a yyyy/mm/dd or dd/mm/yyyy format.

Text Formatting

  • Text strings should be surrounded by quotation marks (“Bob Smith”)

Please feel free to review our more detailed guidelines.

Common Problems

Wherever possible, use a tool or a library to generate your CSV files. Avoid generating them manually.

All strings should be wrapped in quote marks (“), as in the following example:

"This is a string."
  • Remove the thousand separator commas from all numbers (use the plain #######.## format)
  • Don’t use the scientific number format (e.g. 12E3)
  • Remove all currency or percent characters from your numbers
  • For date values, verify that no date is out of range (before 1900 or after 2050)
  • Remove all empty trailing rows from your CSV file
  • Verify that there are no End of File (EOF) delimiters in your CSV. Open the file and check that there are no delimiters at the end of the last line, including tabs or newlines.
  • Bad quotes - a non-matching set of quotes in the file can cause the upload to fail
  • Save your CSVs as “Windows CSVs” on Mac (Macs may use an unsupported end of line character)
  • Don’t use the Finder’s “Compress File” on Mac to create a ZIP file for upload as it adds some hidden files to the archive. Use command line utilities on a Mac or avoid compression

Additional Hints

Using a double quote (“”) symbol to escape a quotation mark (“) inside a given field

This situation occurs when a value inside a field contains quotation marks, which are meant to be entered into the application, such as “Large” Fountain Drink.

Attempting to escape the quotation marks ("Large" Fountain Drink) causes the parser to fail. To properly insert this value with the quotes, use double quotation marks instead (“”Large”” Fountain Drink).

Redundant spaces in a CSV file

Make sure to remove extra spaces between values in your CSV file. Commas used to separate values shouldn’t be followed by an additional space. For example:



Doesn’t work (Note the extra space):

["User_ID", "Name"]

Thanks to your feedback, we have identified these trouble spots, and we are working hard to remove them from the application. Thank you for your patience and support.