Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.

Reply
benjy20
Frequent Visitor

OLE DB or ODBC error: [Expression.Error] The export was exported multiple times.

Hi all,

 

I have numerous PBI reports and all use the same "Dates" xlsx file that I have in my OneDrive, and is referenced to as the WebContents URL. This has worked perfectly for months in both Desktop and Service.

 

= Excel.Workbook(Web.Contents("https://xxxxxxxxxxxxxx/Dates.xlsx"), null, true)

 

For some reason within the last week, when I refresh any report in Desktop, I get the following:

 

OLE DB or ODBC error: [Expression.Error] The export Dates was exported multiple times.. An unexpected exception occurred.

 

I've changed the "Dates" table to a local xlsx as a test and even built the table from a new query as part of the PBI report, so it's not even linking to an external document. I still get the same error when refreshing this table. The refresh works fine in Power Query but the error occurs when refreshing from the main report screen.

 

I can't find anything online for this specific error. Does anyone know what could be causing this since nothing has changed in relation to this document in months, but the error has recently started?

 

Any help would be much appreciated.

 

 

1 ACCEPTED SOLUTION
benjy20
Frequent Visitor

Solved. So it turns out that it was due to the fact my table name in Power Query was called "Dates", as after changing the name of this table to "Date Table", the issue resolved and the refresh worked. I'm not sure what changed within PBI as my date tables have always been called "Dates" and it was never an issue previously.

View solution in original post

1 REPLY 1
benjy20
Frequent Visitor

Solved. So it turns out that it was due to the fact my table name in Power Query was called "Dates", as after changing the name of this table to "Date Table", the issue resolved and the refresh worked. I'm not sure what changed within PBI as my date tables have always been called "Dates" and it was never an issue previously.

Helpful resources

Announcements
Feb2025 Sticker Challenge

Join our Community Sticker Challenge 2025

If you love stickers, then you will definitely want to check out our Community Sticker Challenge!

Jan NL Carousel

Fabric Community Update - January 2025

Find out what's new and trending in the Fabric community.