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

Shape the future of the Fabric Community! Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions. Take survey.

Reply
dporter
Frequent Visitor

Data source error: We're sorry, an error occurred during evaluation.

 

Greetings,

Starting from 2PM Pacific Time on June 21st, a scheduled dataset refresh in the Power BI Service  began to fail at every refresh with an "Error occurred during evaluation" message.  A manual dataset refresh also fails. The dataset refreshes had been working consistently prior to this time and no changes had been made.

 

The dataset's source data is from Dynamics CRM Online.

 

A refresh performed using Power BI Desktop - Latest Version alo fails with the same error. I used the 'frown' to send trace files ro 'pbidesfb@microsoft.com'  Power BI Desktop Version: 2.47.4766.801 64-bit (June, 2017).

 

Error Messages are below :

Porter - Refresh Error 2.jpg

 

 

Porter - Refresh Error 1.jpg

 

 

 

 

 

4 REPLIES 4
apoprio
Advocate I
Advocate I

We have the same problem!!!
This is really happening in the last few days...
We believe that it is a problem in Power BI Service, because when using the same script (Power Query) in Power BI Desktop, the error does not occur and then the data loads successfully!! 

apoprio_0-1639069678385.png

DJTan2006
New Member

Capturar.PNG

Same with me, also retrieving data from Dynamics 365 for Sales. Found this post at https://powerbi.microsoft.com/en-us/documentation/powerbi-refresh-troubleshooting-refresh-scenarios/  

Refresh fails when updating data from sources that use AAD OAuth

CahabaData
Memorable Member
Memorable Member

Not sure this helps, but I had a similar error type when the design didn't change but the data set did change (of course it was a refresh so by definition the data set is changing....)

 

In my case I had a join between tables in what I thought was on one side a table's field that would always have unique values (key field - 1 side of a 1:Many relationship)...and did for awhile so everything worked....but upon a refresh there was a duplicate value coming in from the data source.....  I had to deal with that logic error on my design as it turned out it wasn't a field to be relied upon for unique values.

www.CahabaData.com
v-sihou-msft
Microsoft Employee
Microsoft Employee

@dporter 

 

I can't reproduce this issue. If this issue still persists, please create a support ticket.

 

Regards,

 

 

Helpful resources

Announcements
November Carousel

Fabric Community Update - November 2024

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

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.