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
When the composite dataset is refreshing, the visuals will not load until the refresh is over. This can take easily over 10 mins depending on the dataset. Is there a way to remedy this so the end-user does not think the report has a problem?
We are having a problem with DirectQuery for Power BI datasets for large tables. In the screenshot below 'Account Attributes' has 6M rows and 'Retail Sales' has 24M rows.
Retail Sales is in a separate PBIX file that is loaded on the Power BI service.
When we try to use attributes from the 'Account Attributes' table or refresh the 'Account Attributes' table the report does not refresh. The 'Account Attributes' table would normally refresh in a minute or so but since moving the 'Retail Sales' table to a separate PBIX file the refresh remains in the status shown in the screenshot below and does not complete.
There are no issues when refreshing or using attributes in the report from the other tables connected to 'Retail Sales', such as the 'Date' table. These are all tables that have a few hundred rows.
Is there a service limitation on the size of the tables that can be in separate files?
Looks like I have answered this myself. Will this improve for composite models? 1M rows is a bit restrictive.
2.96.1061.0 (21.08) (x64)
The resultset of a query to external data source has exceeded the maximum allowed size of '1000000' rows.
Microsoft Windows NT 10.0.19041.0 (x64 en-US)
4.7 or later [Release Number = 528372]
Peak Virtual Memory:
Peak Working Set:
Workbook Package Info:
1* - en-AU, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False.
Snapshot Trace Logs:
Model Default Mode:
Performance Trace Logs:
I just now wanted to try this out but cannot get it to work. There is one push dataset I connect to using the latest version of PBI Desktop (the preview flag is enabled). After adding the dataset, `Get data` is greyed-out and I do not have the option to add other data sources.
Like the new Direct query feature and are using it extensively .. however Want to describe an issue we are having that is concerning for us as it makes testing changes to a dataset attached in direct query very difficult
Normally we ..
step1 test modifications we make to a dataset by re-pointing existing ** reports at the modified ‘DEV’ dataset and Verify that they still work correctly .. if all good ..
step2 then we publish overlay ‘Prod’ dataset with dev dataset .. and existing prod reports are good to go
**These reports are normally live connections to same dataset.
Issue is when the report is a Direct Query local Model .. it throws an error in step1 (see below) even when the ‘Dev’ dataset is exactly
The same as prod (so the ambiguous path error we receive is not valid error)… if we go ahead and overlay prod with dev … the prod reports
don’t throw an error and work fine .. but if they don’t I’m afraid we have no way to recover . as we can’t connect to an alternate datasource. In fact I suspect that even if we restored the prior Version of the dataset the direct query local model reports would not be able to connect to it.. and we would have to re-create them basically from scratch
Pls advise if you have heard of this issue and if there is a workaround..
**Note Datasource that we are replacing in the direct query local dataset is an incremental
no ambiguous path .. it is an exact copy of the dataset being used in the direct query model published under a different name in a different workspace.
we had the following scenario:
We created a "golden dataset" that we use in some dashboards. If we now connect an additional data source to the dashboard an extra dataset is created for it, which makes sense, yet we have a strange phenomenon. We have set the permission for both datasets to "Read". But the users can't see the data of the "Golden Dataset" in the new dashboard. Only when we set the permission of the users in the Golden Dataset to "Build", they can see the data. Of course, this is not desired because we want to prevent users from creating their own dashboards with the dataset.
Are you aware of the problem ?
Jeroen — this is the main issue blocking our use of this feature in production. We have MANY datasets and analysts want to add their own lists but build permission is not an option.
This is a known issue, please upvote this idea to help prioritize it:
We have the same behaviour and to my knowledge there isn't another way around it at the moment, which is frustrating...
This is a great feature, when using/testing it I run into the following problem though.
- I connect to an Azure Analysis Services tabular model
- Then I add a calculated column to a fact table using RELATED to add a value from a dimension table within the same model which has a one to many relationship with the fact table, no errors appear when doing this
- As soon as I try to use the calculated column (or something using it) in a visual this error appears:
- The strange thing is that this does work when doing the same thing but with a different dimension from the model (no error appears when using it)
What can cause this error? As far as I can tell I'm not doing something that isn't supported and as I'm referring to a table within the same model I don't see any issues (no limited relationship).
One thing that is different between the dimension for which this works and the one for which it doesn't: the key in the fact table which relates to the dimension which doesn't work has blank values as the dimension isn't applicable for all the rows. In this case I expect RELATED to return a blank value. Also I'm pretty sure this worked when I tested it earlier in the year.
Hopefully you can help me with this, thanks in advance!
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.