Forum Discussion
Refresh not working due to DirectQuery source and calculated table
"We cannot refresh this dataset because the dataset contains calculated tables or calculated columns"
I used two semantic models in DirectQuery mode and then used them to create a summary table using calculated table.
I wanted to not import the tables directly in the dataset again to ensure that the semantic models can be reusable across different reports. However, I am facing this refresh issue and do not know of any workaround that can fix it other than to import the tables directly from source again instead of semantic model.
Hi afaro ,
Thank you for reaching out to Microsoft Fabric Community Forum. Also thank you lbendlin for your inputs.
The error you're encountering occurs because the dataset includes calculated tables or columns while also using semantic models (datasets) as DirectQuery sources. This combination is currently not supported for refresh operations in the Power BI Service.
Calculated tables are evaluated during dataset refresh, but datasets that connect to other semantic models via DirectQuery cannot perform these evaluations during service-side refresh, which leads to the failure you're seeing.
To resolve this, you can either avoid using calculated tables and instead implement the logic using measures or visuals, move the summarization logic upstream into the source semantic models, or switch to importing the required tables if the calculated table is essential. We understand the goal of maximizing model reuse, and we're happy to help you rework the model structure based on these supported patterns.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thankyou.
4 Replies
Hi afaro ,
Thank you for reaching out to Microsoft Fabric Community Forum. Also thank you lbendlin for your inputs.
The error you're encountering occurs because the dataset includes calculated tables or columns while also using semantic models (datasets) as DirectQuery sources. This combination is currently not supported for refresh operations in the Power BI Service.
Calculated tables are evaluated during dataset refresh, but datasets that connect to other semantic models via DirectQuery cannot perform these evaluations during service-side refresh, which leads to the failure you're seeing.
To resolve this, you can either avoid using calculated tables and instead implement the logic using measures or visuals, move the summarization logic upstream into the source semantic models, or switch to importing the required tables if the calculated table is essential. We understand the goal of maximizing model reuse, and we're happy to help you rework the model structure based on these supported patterns.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thankyou.
Hi afaro ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
I had imported two semantic models in DirectQuery modeThat's not a thing. It's either Direct Query Mode or it's Import Mode.
and then used them to create a summary table using calculated table.That pretty much negates the idea of Direct Query. Your calculated table will be recalculated each time a user interacts with the visuals in your report.
other than to import the tables directly from source again instead of semantic modelYou can do either. Sadly, it is possible to import data from a semantic model.
Hi @afaro ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
