Sharepoint folder excel workbooks not recognized?

[zengyong_st]

Hi all, 

Recently when I try to get data from sharepoint folders that contain set of excel workbooks (.xlsx), i am facing error"we didn't recognize the format of your first file (). Please filter the list of files so it contains only supported types ( Text, CSV, Excel workbooks, etc.) and try again."

The same set of folder and excel workbooks previously imported with no issue.

I also tested using excel to open the sharefolder and able to open with no issue.

Seem like this is due to Power Bi.

Anyone facing the similar bug lately?

[Anonymous]

Hi @zengyong_st ,

Please refer to 

Solved: Combining Files Error in Power Query - Microsoft Power BI Community

Workaround to the problem in the dataflow – “We di... - Microsoft Power BI Community

Best Regards,
Community Support Team _ Caitlyn

[zengyong_st]

Hi Caitlyn,

Thanks for the feedback. 
However, i am still at lost.

Previously, the same set of folders and excels workbook is able to imported using sharepoint folders connector just fine.

However, the same set of folders and excels workbook cannot even be loaded, with the error mentioned above.

I have tried using power query in excel to open the same set of folder and excel workbooks, it works just fine.

Hence, I suspect is the bug or error purely related to Power BI.
My power BI is December 2022 version.

Not sure anyone else is facing the same issue.

[YuHash]

Hi, I'm having the same issue.
Seems like after 2022-Nov update, Power BI's Power Query do not recognize Excels in SharePoint folder when you click file combine button.

So instead of relying on helper query automatically prepared which worked fine in the previous version,
I have to create custom function by myself. 
This is no good for someone who does not have knowledge to create custom function.

And even worse, not only in Power BI Desktop but also in Excel's version 2301 Power Query, File combine button throws the same error message (at least in our case).

I cannot understand why this is ignored and not fixed for a few versions already...