Forum Discussion
Refreshes for Datasets containing Calculated Tables over Direct Query to AS started failing Mar 30th
Hi dbeavon3 ,
What I did:
- created a semantic model in fabric
- to add a calculated table, I opened this semantic model in power BI desktop (as the button is greyed out in fabric - acc. to Tom Martens post, that's correct for these thin reports
Solved: New Column in modeling tab greyed out - Microsoft Fabric Community
)
- in power BI desktop I was asked to create a local model in order to make changes on the model
- the local model is based on a direct query
- now, I added a calculated table (which was created in import mode)
- saved in power BI desktop locally in onelake for testing purposes and another time uploaded to fabric directly
- now the new model exists besides the original one
- the new model can't be refreshed because of mixed modes (this helps: Solved: Error message on publishing: "This dataset contain... - Microsoft Fabric Community In this post there is a link to Microsoft docu for composite models
Use composite models in Power BI Desktop - Power BI | Microsoft Learn )
)
- creating a new sso connection on report level caused a sucessful refresh
Yes, at first create the connection in the place of your screenshot. Then select the connection in your report.
I am not sure if this is the solution, but it worked for us.
Kind regards
Ilona
hi Ilona, hope you are well! Thank you for providing this detailed instruction. I am getting this same error where it says "We cannot refresh this dataset because the dataset contains calculated tables or calculated columns based on data from a Single Sign-on (SSO)-enabled Direct Query data source. Please configure the dataset to use an explicit connection with granular access control to access this data source and then try again".
Can you help me a bit more to understand how you were able to create a new sso connection on report level caused a successful refresh please? Thank you in advance!