Importing a standard Excel XLSX file

Comments

7 comments

  • Avatar
    Michael Becker

    Hi Bill,

    check if that Excel is not saved as a template, that often causes this error.

    0
    Comment actions Permalink
  • Avatar
    Bill Tonissen

    No, not a template as far as I know. (I did not build the file. Aren't those .xlst extensions?) I saved the Excel file in tab-delimited format and added it to the cube successfully using the CSV importer. Don't have the time right now to run it down to a root cause.. maybe later.. 

    0
    Comment actions Permalink
  • Avatar
    Marc Saunders

    I personally would save it as Comma Separated (CSV) as tab can have some unexpected results.

    0
    Comment actions Permalink
  • Avatar
    peter liu

    We've found that files saved in the latest version of Excel appear to cause this issue.  We've had to change our Excel files to CSV format.

    0
    Comment actions Permalink
  • Avatar
    Michael Becker

    Hi Peter,

    By latest version you mean?

    0
    Comment actions Permalink
  • Avatar
    Alan Roque

    Hey, 

    That's right, I faced the same issue this afternoon. I had some problems changing to CSV, some data fields were missing after building the elastic cube (null values), so my suggestion is save your time and just save the file as type *.xls  97-2003 it's a workaround that worked for me. 

    0
    Comment actions Permalink
  • Avatar
    Jason Justice

    I was able to workaround this for a previously working XLXS Sisense source file by:

    1. Saving the file as a CSV (I used CSV UTF-8)

    2. Re-saving the CSV file as XLSX.

    I noticed that the problematic Excel file was much larger than the file was after saving via a CSV so perhaps some excessive formatting or blank row/columns is causing an issue when Sisense tries to open it. The XLS 97-2003 also seemed to work, but I did not want to have a mix of Excel formats.

    0
    Comment actions Permalink

Please sign in to leave a comment.