Forum Discussion
There's Not Enough Memory To Complete This Operation
Greetings, to me this seems to be a 'bug' in the memory management of the widgets. I have done this in the past versions with no ill affect but in the past 2 versions this has become an issue.
I have a lot of memory available and I am simply pulling a list of dimension objects in (SSAS MD Cube) into a simple table widget. All works well returning less then 100 rows, 4 columns of data. When I add one more Fact column...memory issue happens. Pull that fact item out and add another dim item (now at 5 columns)...no problem.
Yes, when I filter the data down to a few records it returns fine. However the process to use the UI is to allow the end user to filter down to get a question answered that would imply the initial rendering would not be filtered and should have the capacity to handle, to some real memory limit, a large dataset. This also fails in a similar way when the report is deployed into PBIRS and view via the browser.
Anonymous Were you able to resolve this issue? I have the same problem with the table widget.
yes, you had to change the structure and logic of your data model. I am not able explain it better in english, but try to make new merged tables with some logic and then turn off "load" of old data connections. Or ask some dax profesional how to solve it :-)
This is the solution for this problem if you are having issues using CSV or EXCEL as the data source. For my expereince. My data source is excel and number of data rows is 95k. Power BI desktop is having issues loading the data and returning a memory issue.
Solution: Trimmed down the data to 35k Rows and the issue has been fixed!
Question though : Why Power BI Cannot handle 95k worth of data rows? That is very small in data analytics. Seems like Power BI is just designed to handle small amount of data?
Hi,
There is absolutely no such limit at all. I have dealt with much larger datasets with a lot of ease.
That's what i thought too but after several tries it didn't work until we trimmed down to 35k data rows.
Power BI Bug?
