Data limit suddenly causes error in table visual. Bug in Power BI Desktop June 2025 update?

[Eric7]

After the June 2025 update of Power BI desktop, I suddenly get this error in all my table and matrix visuals where I am using Data limit in the Filter pane:

When I remove the Data limit filter, the tables and matrixes work fine again.

I assume this is a bug?

[szig]

Hello Eric,

Summary of issue: After the June 2025 release of PowerBi I found that my "Data Limit" applied to a Table visual suddenly caused the error:

"Error fetching data for this visual": see details: "When a filter condition uses the In operator with a Table argument, all of the Expressions and all of the projections in the Table must be column references." This error occurred with (I believe) no change to underlying data.

My table had a mix of text, date, and summarized numeric columns.

Mitigation: I was able to find 2 workarounds that worked for my scenario. Each has drawbacks.

• Workaround 1: the most tedious and annoying: I build the report in Desktop with NO data limit and then publish to web. Once published to web, I apply the data limit in the web editor and it worked fine (even with summarized numeric columns). This was a less than ideal resolution because of the manual work required each time I wanted to update my report.
• Workaround 2: very easy and workable for me, but will not work for those who want summarized numeric columns in a table. I re-built my table from scratch with the data limit applied, and noted which columns "broke" the visual (meaning- gave the error mentioned above). Numeric columns were the ones with an issue, and text and date columns had no issue. Furthermore, I tried toggling my summarized numeric columns (i.e. Sum, Average, Count, Median) and found that "Don't summarize" removed the Data Limit error. This workaround will not work if you actually do need summarized columns.

[v-hashadapu]

Hi @Eric7 , Could you please confirm whether the issue has been resolved through the support ticket with Microsoft? If so, we request that you share the resolution or any key insights in this thread to benefit other members of the community.

As part of our follow-up process, we will now proceed to close this thread.

Should you require further assistance in the future, we encourage you to create a new thread in the Microsoft Fabric Community Forum. Our team will be happy to assist you.

Thank you for your cooperation.

[Eric7]

They said that a bugfix will be included in the next release in July 2025.

[v-hashadapu]

Hi @Eric7 , Thanks for the update and sharing the information. Hope your issue gets resolved soon.

Regards,

Harish A

[v-hashadapu]

Hi @Eric7 , hope you are doing well. may i know if you have raised the support ticket as suggested or if your issue's solved from the other suggestions given? If your issue's solved either way, please share the insights here and mark them or any other helpful response "Accept as Solution" so others with similar issues may find the solution easily.
Thank you.

[szig]

I'm having the same issue.

[Eric7 · Accepted solution]

I have reported it as a bug:

https://community.fabric.microsoft.com/t5/Fabric-Ideas/Data-limit-suddenly-causes-error-in-table-vis...

[v-hashadapu]

Hi @Eric7 , Thank you for reaching out to the Microsoft Community Forum.

Thanks for sharing the update. Just a quick note, the Ideas forum is great for feature suggestions, but it’s not really meant for reporting bugs. Since this looks like a bug or regression from the June update, the best way to get it in front of the Power BI team is to raise a support ticket through the Fabric Support Portal. That way, it gets properly tracked and escalated to the engineering team. You can provide them with all the troubleshooting steps you've already taken and error screenshots, which will help them understand the issue better and provide a resolution.

Below is the link to guide you create a Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

[burakkaragoz]

Hi @Eric7 ,

Thanks for reporting this issue with clear details and screenshots. Based on your description, it looks like the problem started right after the June 2025 update of Power BI Desktop and specifically affects visuals where the "Data limit" filter is applied.

This definitely sounds like a regression or bug introduced in the latest update, especially since:

• The same reports worked correctly before the update.
• The visuals function correctly again once the Data limit filter is removed.

What you can do:

1. Check for Updates: Make sure you are on the very latest build of the June 2025 version, as sometimes rapid hotfixes are released after major updates.
2. Rollback (if possible): If this issue is blocking your work, consider rolling back to the previous version of Power BI Desktop until a fix is released.
3. Report the Bug: I recommend submitting this issue directly to the Power BI team via the official Power BI Community Ideas/Bug forum or using the “Send a Frown” feature in Power BI Desktop (under Help > Feedback > Send a Frown). Be sure to reference your screenshots and provide details about your filter setup.

Workaround:
For now, the only workaround is to avoid using the Data limit filter until the issue is resolved, as you’ve discovered.

Next Steps:

• Keep an eye on the Power BI forums and release notes for any updates or acknowledgements from Microsoft about this issue.
• If you find a solution or workaround, please share it here for others who might encounter the same problem.

You are not alone—this is likely affecting other users as well. Thanks again for reporting it!

Let me know if you need help with reporting the bug or finding previous versions of Power BI Desktop.
translation and formatting supported by AI