Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.

Reply
SBX
Frequent Visitor

Data refresh failure due to calculated fields/tables dependant direct query mode

Hi all,  I've created a Power BI report where I've imported two reports from the service (via direct query). These imported models probably have some calculated fields/ tables, hence I'm getting the error below. I know Power BI doesn't support refresh for calculated fields on direct query mode, but I'm hoping there is a solution to this in 2025. I do not want to re-create the same reports via import mode, as that is just duplicating work. There must be an easier way??  

Thanks

 

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":"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."}}],"exceptionCulprit":1}}}

2 REPLIES 2
SBX
Frequent Visitor

Thanks, but not the solution I was looking for.

Anyways, the requirements have changed, so I no longer need the report.

 

freginier
Solution Sage
Solution Sage

Hey there!

 

Since Direct Query Mode does not support calculated tables, consider:

- switching the report to Import Mode.
- Refreshing the dataset manually.
- Recreating calculated fields within the data source (SQL, etc.) instead of Power BI.
How to do this:

- Go to Power BI Desktop → Transform Data.
- Select the dataset → Change Storage Mode.
- Choose Import instead of Direct Query.

 

 

Also, instead of creating calculated columns in Power BI, move them to your SQL Server database.
- Write the calculation directly in SQL (Views or Stored Procedures).
- Then, load the results into Power BI as a normal column.

 

Also since the error mentions SSO, check:
- Go to Power BI Service → Dataset Settings.
- Look under "Data source credentials".
- If SSO is enabled, try disabling it and re-authenticate.

 

Hope this helps!

😁😁

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

Check out the June 2025 Power BI update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.