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 ran som more tests.
Created a calculation group in the model and deployed it to AAS.
When connecting PowerBI to the model I can use the calculation items in new measures definition.
When adding an excel file as extra source (composite model) the measures in the model using calculation items still work. (YTD PY),
and I can use them in new measures definitions on measures in the model too.
But they cannot be applied to the measures (Budget Value) coming from the excel file.
This looks great.
The calculation group defined in the model still works and can be used on measures in the model.
If they don't on the measures from the added source, is acceptable.
Based on this we can continue our developments with the calculation groups.
looking forward to the final version of composite model.
I am very interested in the connetion to Perspective feature which was added with the April 2021 update but I can't seem to find any mention of it in any documentation. Can someone point me to any sort of documentation on it?
not sure what you're looking for - basically when you connect to a PBI dataset or AAS that has a perspective you will see that perspective show up in the navigator when connecting to it.
Please, bring back Direct Query for datasets that connect to SSAS using a live connection. It was working, I have reports built based on that feature and now it's broken and added to limitations - I feel cheated.... I don't agree for it to be a limitation, especially if it was working for some time... That was the only option to work comfortable with Multidimensional Model in Power BI. We bought both Multidimensional SSAS and Power BI from Microsoft and that's ridiculous that Power BI doesn't properly support Multidimensional. Direct Query for dataset that connects to Multidimensiona is the only option to e.g. create a table that has twice the same measure but crossed with Time dimension on different years, or uses hidden measure, that's absurd (you can easily do it in Excel!!!)! Please, enable Direct Query for datasets that connect to SSAS using a live connection (at least for Multidimensional). I know the argument about query performance, but it's better to have worse query performance than not working at all...!
We have been losing the custom 'Sort by column' configuration and data types reverting back to default (ie from numeric to text). This has been causing a lot of frustration and mysterious bugs over the last few weeks and I've seen a few posts alluding to it being caused by this preview feature.
Can someone confirm this is a known issue and when it is expected to be resolved?
Not sure if this was covered, i tried reading through the 246 replies and couldn't really find it.
In our use case, we are finding this feature frustratingly useless:
When we build a power bi dataset that direct queries two other datasets, our workspace admins and workspace members can view the reports and everything works great. After that, our report authors (dataset build permissions) and viewers cannot view anything. Typically the error message we get is couldn't display the visual, sometimes we get an SSO Error (AWSL).
We've tried multiple solutions, but at the end of the day if viewers inside of PBI premium cannot access this seemingly game changing feature, it's of no use.
My question is, is it on the roadmap to correct this? Is there timing available?
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?
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.
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
Did you know that you can visit the Power Query Forum in Power BI and now Power Apps