Forum Discussion
Post PatronUnable to refresh dataset - Error message
Hi bo_afk ,
I have found a similar psot, please refer to it to see if it helps you.
The amount of data on the gateway client has exceeded the limit for a single table.
Actually, the resolution of this issue is exposed in the Error message itself, remove the columns with high cardinality or move to Premium. The easiest way to find the columns with high cardinality is to use the DAX Studio tool:
1 Connect to the model/PBIX file
2 Go to Advanced -->View Metrics
ry to remove as much as you can from the columns that have the highest cardinality. In the above sample if we can remove “Order ID”, it will help reduce the size significantly.
Best Regards
Community Support Team _ Polly
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi bo_afk ,
I have found a similar psot, please refer to it to see if it helps you.
The amount of data on the gateway client has exceeded the limit for a single table.
Actually, the resolution of this issue is exposed in the Error message itself, remove the columns with high cardinality or move to Premium. The easiest way to find the columns with high cardinality is to use the DAX Studio tool:
1 Connect to the model/PBIX file
2 Go to Advanced -->View Metrics
ry to remove as much as you can from the columns that have the highest cardinality. In the above sample if we can remove “Order ID”, it will help reduce the size significantly.
Best Regards
Community Support Team _ Polly
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Advocate IIActually Polly, while your answer is technically correct, it doesn't address the real issue here.
The real issue, which is woefully pervasive throughout the PowerBI Service, is that the standard error messages are far too vague and unhelpful.
For instance, the message that bo_afk experienced, which I myself have experienced quite a number of times, tells us that some table somewhere in the data model is larger than is permitted. That's all. It doesn't tell us which table. It doesn't tell us how far above the limit the table is. It doesn't tell us anything that's actually helpful in our troubleshooting efforts, other than the issue is somehow size related. Even though I'm quite sure that the engine inside the Service knows perfectly well which table, which column(s), and what the storage delta actually is.
Honestly, it wouldn't take a Microsoft engineer half of an afternoon to add this informatin to the standard error message, which would a) save us developers a heck of a lot of our valuable time, and b) save you Community Support Team members a heck of a lot of your valuable time answering questions that shouldn't need to be asked.