Forum Discussion

neillk's avatar
neillk
New Member
10 years ago

Limit on rows being returned

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...
markvsql's avatar
markvsql
Resolver I
10 years ago
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's avatar
    neillk
    New Member
    10 years ago

    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.

    Capture.PNG

     

     

    • WillT's avatar
      WillT
      Community Admin
      10 years ago
      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's avatar
        100RowsLimit
        New Member
        10 years ago

        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.