Gateway_MashupDataAccessError When Running Refresh

[newpbiuser01]

Hello,

I have a report with multiple data tables where the row size is ~ 25 million. These are wide tables, and I've created reports based off these data tables. When I load the report in desktop, I limit the data table with a parameter and set that parameter to be 1000 rows to keep things simple. Once the report is done (without errors) and I publish it to Power BI Service, I update the parameter to be 30 million and run a refresh. The refresh always errors out when I try to refresh using the 30 million, however, when I try to run the refresh with a smaller number of rows, it runs successfully. I also get no errors in desktop. 

I can't understand why I get the error of records not being found for large data tables. Why do I get this Gateway_MashupDataAccessError? I was given to understand that Power BI can easily handle tables with 30 million rows. 

I'd really appreciate any help!

[Anonymous]

Hi @newpbiuser01 ,
Based on your description, it seems that the issue is related to the size of the data table. While Power BI can handle tables with millions of rows, it’s important to ensure that your data source and gateway are properly configured to handle the volume of data you’re working with.
You may want to consider partitioning your data into smaller chunks to reduce the load on the gateway and improve performance .
You can refer to the following documentation to view gateway performance
Monitor and optimize on-premises data gateway performance | Microsoft Learn

Best regards

Albert He

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

[GilbertQ]

Hi @newpbiuser01 

From your screenshot the error appears to be that it cannot find a column called total. If you can double check your day. that the column does exist. Another option is to. just remove the. row limit filter before publishing to the power BI service.

[newpbiuser01]

Hi @GilbertQ ,

The "Total" column in the data table, I've confirmed that. Also, the report refreshes when I limit the data to even  2 million rows, without throwing an error about these columns thereby confirming that the column isn't actually missing.  I removed the data limiting and published the table but get the same error.