Limit on rows being returned

[neillk]

I'm trying to create a matrix where you can view all the customers how you sold to in month. The issue is it cuts the Matrix off after a 100 rows of data. The expand and collapse wont work as im only using customer name and my measures in the matrix. Is this going to be fixed or is this a limit of PowerBI?

[Anonymous]

I created a database view with row limitation. so I did this at the data source level.

[brianjsvehaug]

I've struggled with this issue as well, so I look forward to hearing the resolution.

[markvsql]

Do you mean that you cannot expand the matrix enough to see all the data at once? Or your ability to scroll down goes away? I just created a Matrix in Desktop that has easily about 300 rows and did not have an issue. Can you post an image of what you are seeing?

[neillk]

Sorry for the delayed response, Here is the example, it only shows my Buyers upto C which is 100 rows. the rest gets cut off.

[WillT]

Hi - scrolling down in a table or matrix should continue to load more data. If you're not seeing this, it's a bug on our part so please Send a Frown so we can investigate. Attaching the PBIX file will help immensely if you can!

[100RowsLimit]

Well, with this defect not fixed in the latest 2.31 release, let me bump this thread.

It appears as a major bug in Power BI: data is cut off at 100 rows. 101st row, in our case, shows this error:

DataFormat.Error: OData The format 'application/atom+xml;charset=utf-8' is not supported.

Details: application/atom+xml;charset=utf-8

In Data view in Desktop you cannot see error

but in Query Editor it is shown:

Datasource type: OData feed

Datasource: Project Server reporting database

Please don’t tell that our data is corrupted – it is not. It is possible to retrieve other rows by slicing tables via

= Table.Range(#"Removed Other Columns",1200,100)

and then appending them together in a new table (very nice approach for querying DB, isn’t it?) – this way we are able to build reports.

Corresponding frown with PBIX file and screenshot was sent on Jan 11th, with no any response received so far.

====

Feedback Type:
Frown
Timestamp:
2016-01-11T15:56:21.2815289Z
Product Version:
2.30.4246.281 (PBIDesktop) (x64)

====

Waiting for this bug to be fixed ASAP.

[Greg_Deckler]

I would recommend turning on Tracing, File | Options & Settings | Options | Diagnostics | Enable Tracing and then run a refresh. Go to support.powerbi.com, use the Contact Us link on the right (scroll down) and send them all of the information, including your trace file. This is the official manner in which to submit bugs to support to make sure that they are tracked and resolved.