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.
General Discussions has some can't miss conversations going on right now! From conversations about automation to sharing your favorite Alteryx memes, there's something for everyone. Make it part of your community routine!
I'd built a process not using Alteryx on files delivered from an e-mail scheduled report. I used powershell to extract the datasheet, save as a CSV and then ingest like normal.
When I switched to Alteryx I had the same issue here as something is off with the excel files... From what I can finally deciper, the generated excel files are missing their <?xml declarations, which by opening in excel and re-saving it effectively fixes the formatting to be "correct" and what Alteryx expects. I've battled trying to wire up a powershell script to automate the open and save, but I don't know that's going to be compatible on our server.
On a hunch, I thought about trying these files as .xls or Legacy xlsx... and so far it's worked!
Initially I got a Jet driver error when trying the .xls option - following this information here https://community.alteryx.com/t5/Engine-Works-Blog/Access-Driver-Install-for-xls-File-Acess/ba-p/901... I'm able to fix it. Now I just need it installed on our Alteryx server...
@Muizz did you find a resolution to your issue? I am also experiencing the same problem and I need help ASAP.
Thank you,
Ngoc
Thanks for a good advice!
In my case, choosing "Microsoft Excel 1997-2003 (*xls)" for my *.xlsx file solved the problem.