Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
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
we were unable to reproduce this - can you please open an issue for this so we can collect some more info?
Sure, do you mean I should post it on Issues - Microsoft Power BI Community or should I open a support ticket?
either works - but support ticket is faster.
hmm, interesting, let me talk to the engineers. Thanks for reporting!
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.
Josh Ash
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 brought this up a while ago. Is it being addressed? If so when will it be fixed?
I haven't heard that it's been addressed, but I recommend voting on this idea here:
Microsoft Idea · Directquery for datasets only needs read permissions on all datasets (powerbi.com)
I can confirm it has not been addressed but will be before we declare this generally available.
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.
Hi,
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?
Many Thanks!
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.
I have a model + thin report and need to rename tables from data source, but this breaks the thin report.
How can I update table names referenced in the report?
have you tried opening the report in Desktop and selecting Refresh?
Yes, it refreshes the dataset and shows new table names but that's the problem... all visuals are bronken because are using old tables fields.
Then only solution I got is to manually edit each report pbix Layout file, but it's not very convenient.
For anyone searching, this (dangerous) solution is described here:
I created an Idea to address this question, can you help voting?
Renaming dataset measures can't break client reports (change reference from name to ID)
https://ideas.powerbi.com/ideas/idea/?ideaid=649ec802-682b-ec11-b76a-281878e608e9
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:
Hi,
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?
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
94 | |
86 | |
81 | |
70 | |
49 |
User | Count |
---|---|
143 | |
124 | |
107 | |
60 | |
55 |