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
Go into the PBI service and double check that you have enabled build on all datasets participating in the model. Go to the dataset in the service, click the 3 elipses --> Manage Permissions --> Direct Access --> 3 elipses next to viewer account --> Add Build. Permissions for user should be "Viewer, Build"
at this moment, viewers need build permissions to view reports. we are actively working on changing that, but it is an artefact of how this feature was build (no pun intended).
Ahh, ok. Do you have an ETA on when this feature may be updated? Or an active uservoice record that I could follow for updates?
Ok, since this thread was for feedback I would say I don't find this feature useful at all unless viewers of workspaces/datasets can utilize these types of dataset datamodels. We can't have viewers have permissions to be contributors/members and with PBI premium we cannot license everyone for pro to just view reports.
I get an unexpected result when I add another source, here Excel, to an existing dataset.
In the dataset I have an article dimension to which I want to join more attributes via the Excel file. However, in the Excel table I do not have an entry for each article, which should not be a problem. When I load the Excel file into the model I have the possibility to create the relationship correctly (1:n). All good so far...
If I then use elements from the Excel file and the article dimension in the report, the contents are automatically filtered, i.e. I only get the data records for which entries are maintained in the Excel file. I would have expected a different result here and not a filtering.
If I open the "original" dataset and add the same Excel file to the model, I have the desired behavior in the report, i.e. the additional information is added to the records for which there is an attribute, if there is no attribute, the field remains empty.
I would have expected the same result when joining to the existing dataset.
Is this behavior desired or am I doing something wrong?
I get the following error when refreshing data in Services, even though I enter the credentials:
"your data source cant be refreshed because the credentials are invalid. Please update your credentials and try again"
Does anyone know why I get the error and how I can refresh the data succesfully?
you should be able to successfully refresh. Please check the credentials and if they are correct, please open a support ticket.
Lineage breaks when DQ is turned on to the dataset. It converts over to an Analysis Services source where the url is the workspace and the database is the dataset name. But when looking at the impact analysis of the dataset, these reports do not appear in the list. It would be nice if the lineage could be seamed together.
I was able to use this functionality earlier this week. However today I am not getting the option to update from a live connection to a Direct Query. I uninstalled the desktop and reinstalled. Still no luck 😞
I then tried to start with an excel source query and add analysis services also with no luck. And yes, I have confirmed the Direct Query option is selected.
I should mention also that I am on version 2.91.884.0 64-bit (March 2021)
Hi, I have the same issue, although I have the newest version 2.91.884.0 64-bit (March 2021), I still can't combine two sources: excel imported data and Analysis Services through the Direct Query.
did you enable the preview feature? Also, please note that SQL Server Analysis Services is not supported, just Azure Analysis Services.
Hi 🙂 I enabled the preview feature, but I'm working on SQL Server which is why this feature is not working. Thank you so much for the help!
Ive been testing the updates for Direct Query for Power BI datasets and Analysis Services in Preview at the moment
Previously there were three issues
Connect to Dataset 1 and data set 2.
the folders created within data set 1 and 2 are not in the reporting pbix file (This is now resolved)
The Sort by on fields have been lost in the reporting pbix file (This has now been resolved)
The formatting is lost on data sets.
This unfortunately still seems to be a problem and we absolutely dont want to lose the formatting work set within the data sets
In the dataset this is Percentage 2 for one of my measures, however in the reporting pbix file the formatting hasnt come through
So unfortuantely for us this still isnt fit for purpose. Has anyone else noticed this?
Was this addressed in the June update? Based on the blog I thought it was, but I am still not seeing formatting on my measures flow from the original model to the one with the DirectQuery.
We realized that the activation of this preview feature "DirectQuery for Power BI datasets and Azure Analysis Services" is causing problems in the "Sort by column".
Currently, when we update a report on PWBI Desktop, the columns that are ordered by others, lose this configuration.
We do not make any changes to the structure, just refresh the report.
When disabling the option "DirectQuery for Power BI datasets and Azure Analysis Services", the report updated correctly with the "Sort by column" provided.
This happens with the February and March versions of PWBI Desktop.
It is a correction that you should implement.
Check out the November 2023 Power BI update to learn about new features.
Read the latest Fabric Community announcements, including updates on Power BI, Synapse, Data Factory and Data Activator.
130+ sessions, 130+ speakers, Product managers, MVPs, and experts. All about Power BI and Fabric. Attend online or watch the recordings.