Visual not loading in service but in desktop: Microsoft.Data.Mashup.ErrorCode = 10704

[priyam1]

Hello,

There is a critical business impact for our clients. We have been running multiple reports (scheduled and refresheshed) on a daily basis. Yesterday, we faced an error during visual load for multiple reports across different data sets, interestingly when I download the reports and view it in desktop, i dont see any error and the visuals are being displayed as expected. These reports have been up and running on the server for months now untill yesterday we experienced this error in the server. Please note there were no changes being made to the semantic models. Pasting the error below. Any help would be highly appreciated. Thanks

Expression.Error: We couldn't fold the expression to the data source. Please try a simpler expression.. Microsoft.Data.Mashup.ErrorCode = 10704. ;We couldn't fold the expression to the data source. Please try a simpler expression.. The exception was raised by the IDbCommand interface.

[jlin]

I have been seeing the issue for a few days now and I am seeing it today too.

========

Expression.Error: We couldn't fold the expression to the data source. Please try a simpler expression.. Microsoft.Data.Mashup.ErrorCode = 10704. ;We couldn't fold the expression to the data source. Please try a simpler expression.. The exception was raised by the IDbCommand interface.

Please try again later or contact support. If you contact support, please provide these details.

[a_garcia]

I am seeing the exact same thing, a report that has been working for months (in mixed mode)--> now the direct query part is failing without any reason. When the semantic model is opened in the desktop it works but not in the service. No changes to the code, no changes in the source (sharepoint list), 4300 records stable as we have a process to delete those.  

[a_garcia]

Patched by microsoft as described by their PACE team. 

[leo_97]

It seems the issue has disappeared from the dashboard I'm working on. Has anyone else noticed this on their dashboards?

[christianrb]

I got contacted by our support team. the issue was mitigated this night and we are good again on our side.

[v-nmadadi-msft]

Hi @priyam1  & @christianrb ,

Glad to know your issue has been resolved, please let the community know what additional step has led to that result and mark that reply as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[christianrb · Accepted solution]

We did not do anything. It was fixed by Microsoft since it was a bug with a new release?

[v-nmadadi-msft]

Hi @christianrb ,
We really appreciate your efforts and for letting us know the update on the issue.

Please continue using fabric community forum for your further assistance.
Thanks and regards

[leo_97]

same issues happening and started today out of nothing, reports that have been runing without issues for months .

Error fetching data for this visual

Expression.Error: We couldn't fold the expression to the data source. Please try a simpler expression.. Microsoft.Data.Mashup.ErrorCode = 10704. ;We couldn't fold the expression to the data source. Please try a simpler expression.. The exception was raised by the IDbCommand interface.
Please try again later or contact support. If you contact support, please provide these details.

[adbaum1106]

We are running into an identical issue as well. On ~Friday, any Power BI reporting that is not the file hosted on my desktop where I built out our team's semantic model is not loading, with the same error cited in this thread. This extends to 1) all reports accessed via the Power BI service, 2) all reports downloaded off of the service onto someone else's desktop, and 3) all other reports on my desktop Power BI that are built off of the main report's semantic model. In order to disseminate data to the business, I've been exporitng my desktop Power BI output as a PDF and disseminating it to the organization - definitely a suboptimal interim solution.

Has anyone figured out a solution here? We spoke with Microsoft support and they recommended query re-building, which would be unfeasible given the extent of our buildout. More importantly, though, given that everything was working perfectly just a few days ago and this error appears to have affected multiple organizations, this feels like a Microsoft internal issue.

[g6fonseca]

I’m encountering the same issue. The strange part is that the visualization works fine when I apply a filter (I have a month filter), but the problem arises when I select specific months. This report was working perfectly before, and it uses DirectQuery.

[christianrb]

We do entcounter excactly the same problem with dozens of semantic modells starting arround Friday morning. All in Direct Query mode - Import mode works but is not feasable for our amounts of data. Support is on it but I guess there was something shipped to production Thursday/Friday that limits Direct Query. 

[syerly]

What was 'shipped to production Thursday/Friday'? We are seeing the same errors in multiple reports as of Friday 2.21.25

[KeshaShah11]

I am encountering the same issue. The measure used in the visual, which includes simple calculations like subtraction and division, is generating an error. Is there something worked for you?

[zenisekd]

Hi @priyam1 ,

To better understand the error message, use ChatGPT  🙂 Anyway, the problem, simply stated is that the visual is overloaded by the fields/measures or in direct quer it may be by the queries. It cant handle it with the resources it has in the service, while locally (in desktop) it can. It is possible, that you e.g. have locally more RAM and therefore in desktop it works, but in online it fails.

Try to optimize the query or measures used or filter out some data... 

[priyam1]

Thanks for your response, but I have another concerns as well that these reports have been running w/o any error for the past 5 month, so what could be the possible reason behind this sudden failure.

[zenisekd]

If the data is incrementally growing, maybe it just made the breakeven point... 

[christianrb]

no the amout of data is not the reason - we do have various ammounts per semantic model and all share same problem.

[priyam1]

Yes, but that was already been taken care of at the source itself, but thanks a lot for your response

[v-nmadadi-msft]

Hi  @priyam1 ,
Thanks for reaching out to the Microsoft fabric community forum.
As your error message indicates the query is not folding,
-> Please check in Power BI if the data types in columns are correct and haven’t been changed accidentally which resulted in a mismatch with source datatype.
-> Keep your data model as simple as possible. For example, avoiding bi-directional relationships is a good idea.
-> Try to write your DAX in a different way in the hope that Power BI will be able to fold it.
-> Check if the custom query has any syntax errors in it.

If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS.
Thanks and Regards