I have a report with a table visualization that displays ~57,000 rows of details and is sorted by transaction date in descending order. Everything works as expected in Power BI Desktop.
After publishing the report to the Power BI Service, I noticed many rows are missing from the table. Generally, there are tens to hundreds of transactions per day, and the transaction date column that's sorted on clearly has large gaps. For example, upon opening the report, I expect to see many rows with a transaction date of yesterday, but the sixth row I see is from February (It's sorted correctly, but is missing a lot of data).
If I export the data from the table visualization on the service, there are 41,572 rows in the Excel file.
When I use a slicer to filter the table to transactions in the current month, I then see all the rows I expected to see at the beginning of the table that were missing.
As a test, I added a total row to the table to show the count of the primary key. Interestingly, the transactions from yesterday were shown at to the top, unlike in the previous version. The count was 41,511, still well short of the ~57,000 in the dataset.
Is there a row limit for the table visualization on the Power BI Service?
The report was developed in Power BI Desktop's April 2019 version, and DirectQuery mode is used. The data comes from a SQL Server database, accessed by the service through a data gateway.
