Versions Compared

Version Old Version 32 New Version 33
Changes made by

Yellowfin Admin

Anonymous

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
top
top

...

  1. Import a new CSV file through the Report Builder process
  2. Import a new CSV file through the View Builder process

 

Wiki Markup
{html}<iframe width="700" height="394" src="//www.youtube.com/embed/_esfLmFUCBY?color=white" frameborder="0" allowfullscreen></iframe>{html}
 

 

Import Methods

When importing a CSV file for reporting use, it’s important to consider what the data will be used for, and which import method would best suit that use.

...

Often when working outside of a Development, QA, or Production instance of Yellowfin, you may have a need to import CSV files on a temporary or trial basis. An example of this would be trialling CSV file formats on a temporary setup, or perhaps creating sample content in a Proof Of Concept (POC) type scenario. In this situation you may not want, or be able, to set up a stable database for the purpose of storing CSV data. A temporary solution to this would be to create a writable HSQL database, similar to the one you can install Yellowfin into. In order to do this, follow these steps:

Note: HSQL databases are not stable and should never be used as part of a long term solution.

...

Expand
titleClick to Expand Instructions
  1. Navigate to Administration > Admin Console.
  2. Open the Roles section and click on the role you wish to enable CSV access for.
  3. Enable the following:
    1. Report Types - this provides the user with access to advanced report authoring options, such as CSV Import.
    2. CSV Reports - this gives the user access specifically to the Load CSV File option on the Report Builder's initialisation step.
    3. Advanced CSV Functionality - this allows users to select advanced options, including which writable data source to use, rather than relying on the default option.

      Note: this is an optional role permission.
  4. Save the role.

...

  1. Column Based - ensure the data in your CSV is stored as columns, with no empty columns or rows at the start of the file (if examining through a spreadsheet tool).
  2. Date Format - the date format recognised by Yellowfin is yyyy/MM/dd, so for example: 2014/08/31. If possible, it's a good idea to ensure your dates are stored in this format. Yellowfin does have converters available as part of the import process, but ensuring your dates are in the correct format to start will avoid extra work during import.
  3. No Totals - the CSV columns should not have any column or row totals applied, or other calculations and formats that may be lost during import, or mistaken for data values (rather than totals).
  4. Consistent Data per Column - ensure that the data contained in each column is the same type throughout the file. This will ensure that Yellowfin can correctly identify and assign the field type for each column. For example, if you have a date column, and all the data is dates, except a few records that have the text "N/A", remove the text and leave that empty. This will mean Yellowfin recognises the field as a date, rather than text.
  5. File Format - Yellowfin will only accept CSV files, no XLS, XLSX, or other formats will be accepted.Character Set - Ensure your file uses UTF-8 character set so that Yellowfin recognises all the characters contained in the file.

Don't

  1. Crosstab/Pivot - do not attempt to import data that is in crosstab/pivot format as Yellowfin will examine the file as though it was in column format and as such will store the data in an unintended and unusable structure.
  2. Totals - do not apply totals to your fields, as Yellowfin will not differentiate them from the rest of your data.
  3. XLS - do not store your data in XLS or XLSX formats as Yellowfin will only read CSVs.

...