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
This is mega!
Do we have a view when the next version of SQL Server will be released brining this feature online for tabular SSAS users?
Working on the Product Team for PowerBI must be the coolest job in Microsoft.
it is pretty cool, thanks 🙂 regarding the next version of SQL - not sure, but looking at the speed of previous releases I'd say 2022/2023.
To be blunt, the lack of conformed dimension support, the errors, the bugs, the poor performance on all but tiny datasets... This feature is useless to enterprise customers.
Please prioritise quality over speed to market.
thanks for the feedback - it would be great if you can give specific examples of where you are seeing perf issues, errors, bugs and on which version of Desktop. We have worked on improving performance specifically in the last couple releases of Desktop and our telemetry shows that those improvements are paying off. Curious to learn what you think we need to do as well. Also, not sure what you mean that we don't support conformed dimensions. We are working on a best practices document that explains how to deal with the most common issues people have with this feature.
Has there been any further thoughts around the end user permissions that are required in order to view a published report that has been crafted from a shared dataset under the Direct Query / Local Model?
Having to add a report end user / consumer to the primary shared dataset with Build permissions is an issue. We have analysts that we restrict to shared datasets and in turn they share out their reports to end users. Having the analyst grant users access to the report they created and then turning to the admins to have the end users granted Build permission to the shared dataset is a security issue. These end users could then connect to the core shared dataset and access data they should not be able to view.
I haven't heard that it's been addressed, but I recommend voting on this idea here:
Any idea when it will be declared generally available? I can't see it on the roadmap. We don't allow build permissions so until we can use this with read only access, we can't use it.
We have a dataset that is combing two datasets from separate workspaces. When we renamed one of the workspaces the composite dataset failed, as the connection seemed to be referencing the workspace names, as opposed to the workspace ids. Is this behavious likely to be addressed?
the reference by workspace name is actually by design for technical reasons. We will publish a best practices doc that lists this as well as other things. Sorry for the inconvience.
Looking and playing around i managed to have some cool things about Metric Usage!
Metric Usage are available at workspace level (generate it for one report and you have all reports for the workspace, however you cannot download the pbix) and at admin level (however you cannot make any modification there)
So i was able to create some usage metric (save as a copy) of some specific workspaces (production Workspace of some departments only), connect to these datasets in desktop and in DAX i join the tables via formulas like this one:
I've a scenario where we've country master dataset where row level security is applied to restrict data based on the user's location. We've using this master dataset as a source for another dataset using direct query but the RLS applied isn't getting propagated. Is this by design or a limitation of this feature?
I don't get the option to apply RLS on country table (coming from remote model/dataset) in my composite model. The table name doesn't appear when defining RLS rules in Power BI desktop. I'm not sure if I'm missing anything?
Thanks for the prompt reply. So in a use case like this, I assume using dataflows might be the next best option? Also, are there plans of introducing RLS from remote models to local in the pipeline?
we are looking at the RLS to local thing, but it's a lot of work and to be honest, not a lot of people have asked for it. Please vote on it on ideas if you want this to happen. Dataflows could be a option for you.
After a lot of trial and error, I realized what exactly was the reason for some users not being able to see the report with the composite model. Turns out that only the users for whom "Allow XMLA endpoints and Analyze in Excel with on-premises datasets" is enabled, can see the full report without problems. Others get an error. ("Cant display this visual")
I am sorry to hear that, but it's clearly listed on the blog and docs that you need to enable XMLA / Analyze in Excel. This feature depends on it and cannot work without it.
Check out new user group experience and if you are a leader please create your group!
Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.
Click here to read more about the July 2021 Updates