Power BI has a known bug with Direct Query reports which has large records Ex: 300,000 rows from a SQL source where only subset of records are displayed in a Power BI tabular reports and rest other records are silently skipped. The export to excel also maxed out at 30,000 records for a reports with 31 columns. Recently PowerBI has released a fix to address the row count descrepencies with the source by throwing an error if the size of rows is above ~30MB which this seems to cause a bigger problem where all our direct query reports error out with below message. I could replicate this issue even with 30,000 rows now
The amount of a single row data on the gateway client has reached the maximum MB size for a single row. You will need to determine what the row is from your data source and attempt to filter it out or reduce the size for that row.
We approached Power BI Support team and understood this fix is rolled out to Shared Space and asked us to try Premium Space. Did any one else have similar issue with PowerBI Direct Query reports with larger data?
We moved our workspaces to Premium capacity and reports are loading fine but understood from support team the fix to error out reports if its unable to load all reports data from source is going to be rolled out to Premium space which is concerning as this is not a right fix and need to be addressed in a better way.
v-xiaoyan-msft
on:
"Sort by column" should work regardless of key col...
on:
100% stacked column chart - Detail label font colo...