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
I find if you go to transform data, data source settings, and add another table to the composite data source, it refreshes the session and you can continue working in it (just delete the table you added).
I noticed that the following is still a limitation
When is it expected that this will be fixed? It's quite a dealbreaker for us, since the reports show up with wrong formatting!
I am facing the following scenario:
I am connected to 2 datasets in a composite model. These 2 datasets use direct query both of them. In the composite model I create relationships between tables in the 2 models. One thing I notice is that formatting on measures is gone. F.eks, in dataset a measure is formatted as percentage 3%, whereas in composite model same measure shows 0,03 when used in reports. Or in dataset a measure is formatted as currency with no decimals, and in composite model same measure shows without currency and with decimals. Date columns modify their formatting. Columns that should not summarize, all of a sudden sum. Also, descriptions of measures and columns are not there in the composite model either.
it will be fixed in a future update. I am not at liberty to say here which, but we're shipping it soon and the update will be there before this feature becomes generally available.
I have the similar issue like the topic listed below of refreshing the composite model dataset in service :
everything works fine for calculated table in desktop mode. However, when the dataset is published to the service, there will always be an SSO error message
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?