Forum Discussion
DataFormat.Error: The input couldn't be recognized as a valid Excel document. Details: [Binary]
Hi,
I had a report that was working daily (>365 days) until today.
Today it no longer runs and has the error below.
Nothing has changed in the source or the PBI Report. Could somebody please help?
Thanks
S
7 Replies
- AnonymousNot applicable
Thanks but doesn't seem to explain. I'm working on it further, strange.
It's a Excel 365 document which is populated from a Power App if that helps explain?
S
- AnonymousNot applicable
HI Anonymous,
I'd like to suggest you download the file to the local device and use an excel connector with that file to confirm if this issue is related to the data connector or the file itself.
Regards,Xiaoxin Sheng
- AnonymousNot applicable
Hi Anonymous,
Any update for these? Did the above suggestions help with your scenario? If these also don't help, please share more detailed information to help us clarify your scenario to test.
How to Get Your Question Answered Quickly
Regards,
Xiaoxin Sheng
- AnonymousNot applicable
Hi,
No still no solution on this, just had to use a workaround due to time constraints, I've identified it must be the file and not the connectors.
S
- AnonymousNot applicable
HI Anonymous,
Ok, thanks for sharing the response about this issue.
In addition, if you can't find the root cause of this, you can also consider submitting a ticket to get further support from the power bi support team. (it is free for pro and above license)
Support | Microsoft Power BI
Regards,Xiaoxin Sheng
- agnieszkaRegular Visitor
Hi All,
I have struggled with the same issue. But didn't want to give up and finnaly resolved it!
My situation: I was getting xlsx file (with no table, just 1 sheet in it) inot my outlook every day.
This was essential file for my Power BI, to be updated every day.
After moving file to OneDrive or to Sharepoint, I was getting an error msg : Details: "The input couldn't be recognized as a valid Excel document." .
Solution: After speaking to a sender of this xlsx file , checking few things (like opening the file via notepad++) showed us that coding of that xlsx was incorrect.
The file was changed from xlsx to csv with UTH-8 encoding.
And everything is working just fine now.