Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and a 50 percent discount on exams.
Get startedEarn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
Can anyone else confirm this behavior?
Hadn't tested this in a while but converting from Live to DirectQuery for Power BI Datasets and AS seems to be broken at least in the latest release of Power BI Desktop.
First, this feature is enabled in Preview features and in the Service for the entire organization.
If I start with a Live query, I do not get any option to make changes to the data model or add a local data model as described here: Using DirectQuery for datasets and Analysis Services (preview) - Power BI | Microsoft Learn
Solved! Go to Solution.
It's working for me as expected. Are you sure the dataset you're connected to is the "root" dataset and not another version of an existing dataset? There's a limit of the chain - I think it's 3 currently.
Also few other things to check - do you have build permissions on the original dataset?
Is XMLA endpoint enabled in the tentant and so is Analyze in Excel?
@JirkaZ You know what, I just realized what the issue is. I had datasets of the same name published in a Workspace as well as in My Workspace. Doesn't work for My Workspace datasets, only datasets in Workspaces other than My Workspace. Duh. I was accidentally connecting to the dataset in My Workspace.
@Greg_Deckler: Does this feature need to be enable for the entire organization, or it can be activated for dev team only?
Thanks
@JackP That tenant setting can be enabled for specific security groups or to exclude specific security groups.
@Greg_DecklerWe did activate it for a specific security group for dev team.
But for other users, would they be able to open reports using this feature (report and dataset published on premium capacity) ?
Or all users need to be included in this setting?
Thank you
It's working for me as expected. Are you sure the dataset you're connected to is the "root" dataset and not another version of an existing dataset? There's a limit of the chain - I think it's 3 currently.
Also few other things to check - do you have build permissions on the original dataset?
Is XMLA endpoint enabled in the tentant and so is Analyze in Excel?
@JirkaZ You know what, I just realized what the issue is. I had datasets of the same name published in a Workspace as well as in My Workspace. Doesn't work for My Workspace datasets, only datasets in Workspaces other than My Workspace. Duh. I was accidentally connecting to the dataset in My Workspace.
User | Count |
---|---|
88 | |
73 | |
69 | |
64 | |
56 |
User | Count |
---|---|
98 | |
92 | |
84 | |
74 | |
66 |