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.
Here are some areas that we'd like to hear about in particular:
Thanks and we look forward to hearing your feedback!
- The Power BI Modeling Team
Build Permissions Required on any dataset connected via Direct Query to Analysis Service?
This is a documented requirement. However, it has unintended ramifications. For example, when I connect to my HR dataset, I can publish only metrics that are not sensitive on my local dashboard. However, due to the requirement to have Build permissions directly on the HR dataset I have now exposed the full HR data model (via Power BI Desktop or Excel) to any user of my dashboard. This seems like an overshare and a security risk.
It is unfortunate, I feel like in it's current state it's unusable for Power BI Premium subscribers (with the potential re-use, it seems like enterprise deployments would benefit the most).
I would recommend voting for this feature on uservoice: Microsoft Idea · Directquery for datasets only needs read permissions on all datasets (powerbi.com)
I hope this will be fixed in near future. I just started to use these new features and now it feels a little frustrating to realize all the end-users would need build rights to use the newly created reports.
Modifying the Direct Query to Analysis Services connection deletes all Joins and Measures created in the local model
Updating the Direct Query to Analysis Services connection to a new dataset in the same or new Workspace with exactly the same data model causes the local model to delete all related Measures and Joins created in the Local model. As a result when initially building a model against a Test data model, all Measures and Joins need to be recreated after connecting to the Production data model.
I was wondering if there is a limitation with Premium Workspaces whereby you cannot use the recently released feature of direct querying datasets within premium workspace.
I have successfully connected multiple datasets which sit in non-premium workspaces but when I try and connect to a dataset within a Premium workspace I get the below error, and it is not a permission issue as I am the admin of the workspace:
Any help resolving this would be greatly appreciated otherwise I guess I will have to have a non-premium workspace for reports and premium for dataflows.
Thanks in advance!
Currently connecting to AAS live and it works in PBI Desktop and PB Service. When I change this to Direct Query so that I can do more with the model by adding new measures outside of AAS, it works in PBI Desktop, but I get a "Cannot Load Model" in PB Service.
I had someone someone check to ensure the endpoint is active, along with live connections in the Tenant settings are active. Any thoughts on what else this could be?
This is holding up a project for a client.
@jeroenterheerdt , I see you have helped others, any insight?
We're migrating from a SSAS Multidimensional on premise to Azure Analysis Services (Tabular),
Composite Model is a very interesting feature for our end users, but I would like to use Calculation Group in our model.
In the Preview the combination of Composite Model and Calculation Group is mentioned not to be supported.
'Calculation groups on remote sources are not supported, with undefined query results.'
Will it be supported in the (near) future?
Does it make sense to add Calculation Group to our model?
Thanks for your interest in the feature, we're still working through a couple of things, this is one of them. However, depending on how you use it this is not going to be supported or might be. In essence, defining a calc group on a remote source is not supported (and I don't think it will soon). However, you will soon be able to define calc groups on your local model.
What do you mean by calculation group on remote source is not supported ?
do you mean in combination with Composite Model ?
I defined a Calculation group in my model, deployed it to Azure Analysis Services and it works fine.
similar when deploying it to on-prem Analysis Services
with remote source I mean a AAS or PowerBI dataset that you connected to using DirectQuery: using a calculation group on such a source is not supported.
I ran som more tests.
Created a calculation group in the model and deployed it to AAS.
When connecting PowerBI to the model I can use the calculation items in new measures definition.
When adding an excel file as extra source (composite model) the measures in the model using calculation items still work. (YTD PY),
and I can use them in new measures definitions on measures in the model too.
But they cannot be applied to the measures (Budget Value) coming from the excel file.
This looks great.
The calculation group defined in the model still works and can be used on measures in the model.
If they don't on the measures from the added source, is acceptable.
Based on this we can continue our developments with the calculation groups.
looking forward to the final version of composite model.
I am also working with composite model with Direct Query for Power BI Datasets, and with some calculation groups. I was delighted at first to see that this combination seems to work! 😊
But althought this works well for me in the desktop, once published to the service I cannot refresh the model, and get this error:
I have not added any columns nor calculated table (other than the calc group) to the DQ dataset. So I am thinking I hit the imitation here.
Do you have the same behavior?
It looks pretty close to work, but if we cannot refresh the model, well, it's useless.