Forum Discussion

tessahurr's avatar
tessahurr
Microsoft Employee
5 years ago

Share your thoughts on DirectQuery for Power BI datasets and Azure Analysis Services (preview)

Hit Reply and let us know what you think of the DirectQuery for Power BI datasets and Azure Analysis Services.  To learn more about this feature, please visit this blog post or our documentation.   ...
General Comment
jeroenterheerdt's avatar
jeroenterheerdt
Microsoft Employee
4 years ago

correct, this is an existing limitation.

charrington's avatar
charrington
Advocate V
4 years ago

Thanks for the answer.

1) This DQ on datasets is such a nice feature! But many organizations, including ours, are using the powerful calculation groups as well. Please enhance this in future release, I am sure this will be problematic for many to not be able to combine both.

 

2) Also I just tested the refresh on the service after deleting my calculation groups from my pbix with DQ and import...I still get the same 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}}}

 

Again I haven't added any column on the DQ table, nor calc table, nothing...so I don't understand. I'll test more of course. Maybe the calc group added then removed? This is a bit scary...cause my entire solution is built, working well, but I cannot refresh. I don't understand what is it trying to refresh thought...? this is direct query so refreshing makes no sense in the service.

Any advise?

Christian

  • charrington's avatar
    charrington
    Advocate V
    4 years ago

    I'll reply to myself 🙂

    maybe it will interest someone else.

     

    Think I found the root cause of this issue, but can't find the workaround so far.

    Ok so at first I had that setting to auto create time intelligence data table on my pbix. When working with direct query based on AS Dataset, it seems those dates table are still created, not sure why, but they are, and it's clearly referencing my Direct Query:

     

    I think that could be the issue. In the service, that table seems like a Calc table, and since there is the limitation on calc tables cannot be refreshed with DQ, this throws the error (see above).

     

    Now I think if I remove those local data table (which I even don't use!) it might work.

    Based on this link they are supposed to be gone when it's turned off.

    However that doesn't work...my local date tables are still showing...I cannot delete them with DAX studio, Tab Editor...how to delete those tables?

    Not certain it's the issue, but that would make sense.

     

    By the way, I created a new more light model from scratch, with some similar scenario, DQ and import, so composite, without the auto time set, and...well, first the local data tables are still present (!) and second, for some reason, when published in the service, I am now able to refresh, it works! Problem of course is my whole complex model still have the issue, restarting from scratch would be really painful.

     

    Obviously DQ on datasets is still in preview, and some things are not so clear. 

    But there is some logic there that starts to make sense with those dates table...anyone?

     

    Thanks

    Christian