Refreshes for Datasets containing Calculated Tables over Direct Query to AS started failing Mar 30th

[AugustoChaves]

Hello, 

Refreshes of datasets that contain calculated tables from DQ to AS started failing March 30th, 2022. This worked completely fine until March 29th which points to a change at Power BI service side. The error message is as follows:

{"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}}}

[AugustoChaves]

Hi, I only have the number of the support ticket that was opened last year, 2203310040005513. Unfortunately I don't have the ICM#.

[andrewtuplin]

I've tested this a few different ways and I've found the specific condition that causes refresh to fail. 

If you create a table in DAX that references a Power BI Dataset (i.e. a dataset outside of the the report being used as a dataset) refresh will fail. 

For example. Say I have a dataset in the Service called 'DIM Date'.  In my report, I can add that Power BI Dataset as a datasource and, in fact, I can add multiple external data sources, and I can also add local data sources in both DAX and Power Query.  What I cannot do is create a table in DAX that references a Power BI dataset.  For example, if I create a new table as: 
MyDate = 'DIM Date', the report will not refresh in the service. 

[frw]

I just wanted to say thanks, because this advice solved the problem for me. I had a calculated Date table based on a summary table accessed through DirectQuery. Switching it to a hard-coded calendar range, while inelegant, fixed the error message I was getting.

It's bonkers to me that this issue exists in the first place. I can reference these DirectQuery tables in measures and manipulate them in so many ways, but any reference to them in table/column construction screws the whole thing up.

[andrewtuplin]

This is an issue for me as well. 

[Anonymous]

Hi all, do you have any news related to this topic?
I spend last two week by building report with calculated tables based on DQ and finally I get same error as you. 

Which solution you used to step around it?

[Prateeksha11]

Is there any update/solution to this? Still facing this error currently and need a fix for it.

Thanks,

[rajeswar_j1022]

Hello

Are you finding any solution for this issue, I am also facing same issue.

Would appreciate if a solution is identified.

Much Appreciated.

[kymramosrpo]

Hello everyone,

I, too, built a couple of calculated tables with data directly querying a Power BI dataset, only to find out that the report will fail to refresh once published in the service.

The workaround I came up with is not perfect but it works (also, this alternative might only work for smaller datasets...):
(1) create a flow in Power Automate to get the data from the PBi dataset and export as CSV* (way faster and simpler than exporting as an Excel spreadsheet) > (2) query the CSV file instead

My flow uses the Recurrence trigger, I just arranged the order of refresh and trigger schedules.

*Reference: Automatic exports of Power BI data 🤖 | Run a query against a dataset - YouTube, Curbal, @ruthpozuelo, Jun 20, 2022

I hope this helps!

[BeAStar]

was there any solution to this??? I've had reports that were auto refreshing without any issues and suddently they show this error.

[faroukwahsh]

There's already an Idea posted by a Microsoft employee reagrding this Premium_ASWL_Error - Single sign-on (SSO) credenti... - Microsoft Power BI Community

Please go in and vote on it. 

[AugustoChaves]

This is not the same thing. Calculated Tables from a DQ Dataset used to work until March 29th, 2022 and then stopped working after an update. SSO is not in play here.

[faroukwahsh]

Odd, refreshing a report with a calculated table that references a DQ to a PBI Dataset never worked for me on the service. Now I am thinking it might be source specific since you mention this wasn't an issue for you before. 

[AugustoChaves]

It would fail refreshing from Power BI Service but connecting through XMLA endpoint and processing the Database it worked.

[GSE]

Hi @AugustoChaves ,

do you remember which mode you used? Process Full runs into the same error that I would get when refreshing the dataset from Power BI Service ("Refresh is not supported for datasets with a calculated table or calculated column that depends on a table which references Analysis Services using DirectQuery"). And Process Default and Recalc don't seem to update the data in the report.

Best regards

GSE

[Nathan_C]

Hi @AugustoChaves  

Have run into the same issue with a calculated table build off of two DQ tables.  The table was being used as a data source for a paginated report hosted on PB Service.  

I do not have a solution for issue but have eliminated the calculated table by pulling it in as its own DQ table, and I'm no longer receiving the gateway error upon refresh.  So to me this would point the issue to being the calculated table.  I did not attempt to try creating the calculated table through an other manner within Desktop.  

Would appreciate if a solution is identified or the issue is resolved that you update this thread with the outcome.

Much Appreciated.

[AugustoChaves]

Hi Nathan, I have a support ticket opened and it's confirmed it's a bug/requires a fix. I'll post here when I get a response. Thanks

[AugustoChaves]

Hi GilbertQ, the gateway was already updated to latest version, March 2022, but that shouldn't have an impact since this is DQ to a Power BI Dataset (DQ to AS).

Thanks

[jamezcua9]

Posting to keep the thread alive. 
Still facing the issue IN 2024. Any roadmap to have a resolution on this? 

[StijnVnb]

Hi @AugustoChaves , any news or update from Microsoft? Did they communicate a timeline for the fix? Regards, Stijn

[AugustoChaves]

No timeline. Support is very poor and takes a long time to break 1st layer barrier.

I'm pressing for a date and will post here when I hear.

[GilbertQ]

Hi @AugustoChaves 

It could possibly be that there has been a change in the underlying calculated table?

There are often is changes to the Power BI Service. 

What happens if you try this on PBI Desktop does it work there too (Using the latest version of PBI Desktop)?