cancel
Showing results for 
Search instead for 
Did you mean: 

SCHEDULED REFRESH ERROR WHEN USING DATASET CONNECTION

Data source error: {"error":{"code":"Premium_ASWL_Error","pbi.error":{"code":"Premium_ASWL_Error","parameters":{},"details":[{"code":"Premium_ASWL_Error_Details_Label","detail":{"type":1,"value":"Refresh is not supported for datasets with a calculated table or calculated column that depends on a table which references Analysis Services using DirectQuery."}}],"exceptionCulprit":1}}}
Cluster URI: WABI-SOUTH-CENTRAL-US-redirect.analysis.windows.net
Activity ID: 954fd614-029c-451f-ab77-aac648a599e3
Request ID: 02fb20e5-43e4-376e-ccc8-b07440f335f0
Time: 2023-01-12 10:31:06Z

Status: Investigating

Hi @BRNS 

It sounds like you are trying to refresh a Power BI dataset that includes a calculated table that depends on another table that uses Direct Query mode to connect to an Analysis Services data source. Unfortunately, Power BI does not currently support refreshing datasets that include calculated tables that depend on tables using Direct Query mode.

One solution you could consider is to change the source data for the calculated table so that it does not use Direct Query mode. This would allow you to refresh the dataset, but you would need to find a way to incorporate the data from the Direct Query source into the calculated table using other means, such as using Power Query to merge or append the data.

Another option is to use a separate dataset for the calculated table, and then use a measure or a report-level filter to control the data displayed in the report based on the data in the calculated table. This would allow you to refresh the main dataset without affecting the calculated table.

It's also worth noting that Power BI recently introduced the ability to refresh datasets that include calculated columns, so you may want to consider using calculated columns instead of a calculated table if that meets your needs.

 

Best Regards,
Community Support Team _ Ailsa Tao

Comments
v-yetao1-msft
Community Support
Status changed to: Investigating

Hi @BRNS 

It sounds like you are trying to refresh a Power BI dataset that includes a calculated table that depends on another table that uses Direct Query mode to connect to an Analysis Services data source. Unfortunately, Power BI does not currently support refreshing datasets that include calculated tables that depend on tables using Direct Query mode.

One solution you could consider is to change the source data for the calculated table so that it does not use Direct Query mode. This would allow you to refresh the dataset, but you would need to find a way to incorporate the data from the Direct Query source into the calculated table using other means, such as using Power Query to merge or append the data.

Another option is to use a separate dataset for the calculated table, and then use a measure or a report-level filter to control the data displayed in the report based on the data in the calculated table. This would allow you to refresh the main dataset without affecting the calculated table.

It's also worth noting that Power BI recently introduced the ability to refresh datasets that include calculated columns, so you may want to consider using calculated columns instead of a calculated table if that meets your needs.

 

Best Regards,
Community Support Team _ Ailsa Tao

ManuGP
Frequent Visitor

If this is "not supported" shouldn't there be a warning when creating this type of formula in PBI desktop? It is sort of treacherous that it allows you to build this setup in PBI desktop working perfectly fine and that you only realize it wouldn't work after you publish and try to refresh.

 

According to various users in this thread: https://community.powerbi.com/t5/Service/Refreshes-for-Datasets-containing-Calculated-Tables-over-Di... this worked perfectly fine and stopped working during 2022. 

 

In my particular use case we have fact tables from separate PBI datasets in the workspace and we create composite models joining together the different fact tables and to build dimensions tables we have the calculated tables with SUMMARIZE or SUMMARIZECOLUMNS DAX functions (in this way we have en easy and effective way to have the smaller possible dim tables while ensuring referential intergrity).

pavel_lazarov
Regular Visitor

Same problem:
On the Desktop Application everything in the report is working. Just published in cloud it is still working. Once refreshed (online) gets broken!

Same as @ManuGP position.