This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I'm having problems reading Excel files (.xlsx) downloaded from the internet.
Using the Input tool, it's unable to read sheets when I try to "Select a Sheet".
The tool works when we open the file manually and save it before adding it to Alteryx, however, for freshly downloaded files, we get the above problem. Obviously this leads to challenges when it comes to automating our workflows.
Has anyone faced this issue, and if so, how was it solved?
**PS: would upload a sample file, but it contains confidential data, and altering it would fix this issue (Catch-22)
Can you outline your physical workflow (not the alteryx part, but how the file comes to exist on your system). Tough to diagnose problems like these without source but some additional questions might help us narrow it down.
If you're saying its an excel file being downloaded from the internet but it contains proprietary information, are you pulling it out of OneDrive or an internal blob storage service?
Is this an automated report generated by some other piece of software or an excel file created the old fashioned way?
Does opening the file and not saving any changes fix it, or is it only fixed when you save the file again?
Does excel notify you that there is a problem with the spreadsheet when you open it?
I'm wondering if it's something with doctype related to the download that alteryx doesn't fix natively, but I've never ran into this specific issue before.
The file is an automated report generated by another piece of software that's automatically uploaded to an FTP.
We setup (python) scripts to download the file from the FTP at intervals. We got around this problem previously by setting up the scripts to open and save the files automatically once the downloads were done, but we're trying to move away from the scripts and automate the whole process in Alteryx.
Opening the file alone does not solve the problem, the file needs to be saved for it to appear in Alteryx. We don't get notified of any errors when opening the file in Excel or Tableau (although in excel the file is opened in protected view until we enable editing and save it). This is something we have come across only in Alteryx.
Is it possible that there is corruption at the automated report or the FTP download level? It sounds to me like it's trying to force something like a .csv to be an .xlsx file. Similar to how you can change the file extension of something without actually opening and saving as a new file type.
For instance, you can rename a .txt file to be .xlsx and when you open it you receive a "File may be corrupted" error that goes away when you save it from the open file into the proper .xlsx format.
If you have the ability to change the output from the automated report I would play around there. . .
I am having a similar issue to Muizz for Excel reports downloaded from OneSource or Longview. They download as .xlsx from the site, and open fine on my computer, but Alteryx does not recognize the file until i re-save the file (still as .xlsx) onto my computer. I don't believe it's a corruption issue where these files are exported in another format because they open in Excel just fine. It seems to only be an Alteryx nuance. Any help you can provide is appreciated!