Users working with reports occasionally encounter the error “Query exceeded memory limit.”
However, report creators have no way to determine which specific query caused the memory limit to be exceeded.
It would be helpful to have a feature, such as in Fabric Capacity Metrics, to identify which queries caused the memory limit to be exceeded.
No CommentsBe the first to comment
Recent ideas
Power BI UX Suggestion: Preserve Selection When Switching Between Report and Model Views
When developing a Power BI report, if I select a visual in Report View and then switch to Model View, the selected table/column context is lost and everything becomes unselected. This can be inconv...Murtaza_Ghafoor8 hours agoSuper UserNew9Views0likes0CommentsPower BI UX Suggestion: Preserve Selection When Switching Between Report and Model Views
When developing a Power BI report, if I select a visual in Report View and then switch to Model View, the selected table/column context is lost and everything becomes unselected. This can be inconv...Murtaza_Ghafoor8 hours agoSuper UserNew10Views0likes0CommentsDefault Scrollable Time-Series Charts to Most Recent Data
Currently, Power BI time-series charts always open scrolled to the earliest (leftmost) date by default, which is inconvenient for reports where users are interested in the most recent (rightmost) dat...CStillwell10 hours agoNew MemberNew8Views0likes0CommentsPower BI Desktop Data Load: Can We Get Better Progress Visibility?
One UX improvement I’d really like to see in Power BI Desktop is better visibility when loading large datasets from Power Query. Currently, when Power Query finishes processing and the data starts l...salmansaifee7711 hours agoRegular VisitorNew20Views1like0Comments