Forum Discussion
"The input couldn't be recognized as a valid Excel document."
I have this error but it seems to be computer specific, or more accurately Excel version specific. Using the same source files, a Power Query | Combine Binaries will work from one computer but not another.
Using Excel 365 ProPlus version 1701 build 7766.2071 (First Release for Deferred Channel) it works fine.
Using Excel 365 ProPlus version 1609 build 7369.2127 (Deferred Channel updates) I get the "The input couldn't be recognized as a valid Excel document." error. Updated from Current Channel to version 1702 build 7870.2038 and the Combine Binaries worked without error.
Scope: Combine Excel rows from multiple similarly formatted excel sheets into one.
- MTOct 03, 2020Copper Contributor
this error is specific to excel 2016 whereas i did not observe the same in excel 365.
Any suggestions?
- SergeiBaklanApr 20, 2017Diamond Contributor
Hi Todd,
Combine Binaries starts working with Excel workbook formats from January this year https://blogs.office.com/2017/02/08/january-2017-updates-for-get-transform-in-excel-2016-and-the-power-query-add-in/, i guess from build 7668.2066. On earlier builds it worked only with CSV (or txt) formats.
I have no old builds available and can't check how Combine Binaries worked before. Now it in most cases correctly recognizes file format and use Excel.Workbook or Csv.Document functions depends on file format. Perhaps on earlier version connector was not so clever and gave an error what can't recognize the format.
That's easy to check if try to open Excel workbook by From File->From CSV, exactly the same connector as within Combine Binaries.
Anyway, that's bit different story. In brief, in your situation PQ analyzes which actual format the file has and, if can, use proper connector independently on which UI menu you use to connect the file (latest builds) or give an error (older builds).
In my case we connect to the file with proper connector which has to work with our file format, but PQ can't parse the file due to internal errors in XML structure of the file (more exactly, non-standard XML configuration from PQ point of view).
- Rigers DibraSep 11, 2018Copper Contributor
I face the same problem. I don't know why first 3 tables are ok, but the next two no. How can I fix this?
- Oct 20, 2018Did you try the solution provided by Sergei in his first post?
"it's enough to open the file in Excel and save it (without any changes) – Excel is clever enough to fix the scheme."