Forum Discussion
Refresh failure in services for SharePoint data
Your issue sounds similar to the issue I saw on another post.
I am pasting the response from GilbertQ .
It could well be that when you are creating this table (if the underlying data is large) it could cause it to consume a lot of memory.
This is because when you create a calculated table inside the Power BI dataset this is uncompressed and can consume a lot of memory.
The reason it could work on your desktop is because you are only limited by the amount of memory on your desktop which could be 8 or 16 or 32GB of RAM (Memory), whilst in the Power BI Service it is limited.
If you remove the table and it refreshes try and re-create the table in Power Query, this will allow the table to be compressed before it goes into the Power BI datasetCheck for (1) Size of the dataset you are loading (2) Check your premium capacity limit (3) Avoid calculated table at Dax level
If this post helps, then please consider Accept it as the solution, give Kudos!
Your issue sounds similar to the issue I saw on another post.
I am pasting the response from GilbertQ .
It could well be that when you are creating this table (if the underlying data is large) it could cause it to consume a lot of memory.
This is because when you create a calculated table inside the Power BI dataset this is uncompressed and can consume a lot of memory.
The reason it could work on your desktop is because you are only limited by the amount of memory on your desktop which could be 8 or 16 or 32GB of RAM (Memory), whilst in the Power BI Service it is limited.
If you remove the table and it refreshes try and re-create the table in Power Query, this will allow the table to be compressed before it goes into the Power BI dataset
Check for (1) Size of the dataset you are loading (2) Check your premium capacity limit (3) Avoid calculated table at Dax level
If this post helps, then please consider Accept it as the solution, give Kudos!