cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
tessahurr
Microsoft
Microsoft

Share your thoughts on DirectQuery for Power BI datasets and Azure Analysis Services (preview)

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:

  • Performance
  • Query editor experience--the remote model query doesn't show up in the query editor and only in the data source settings dialog. What are your thoughts?
  • Navigator experience
  • Thoughts around governance and permissions for models that leverage this feature
  • Nesting models, i.e. building a composite model on top of a composite model
  • Automatic page refresh for live connect in composite models

Thanks and we look forward to hearing your feedback!

 

- The Power BI Modeling Team

494 REPLIES 494
WaleyWang
Helper I
Helper I

Hi, all,

I have one report using data imported from databases. And another team developed a report which gets data from hundreads of excel files, I need the same data and don't want to bother myself to import the data again, so I tried to connect their PBI dataset instead. Which created a "composite model" and I failed with this solution due to the following 2 problems encountered:

(1) I couldn't set refresh schedule for my dataset due to the credential setting error:

快照44.jpg Seems that this is a known issue, but when can it be fixed? (https://docs.microsoft.com/en-us/power-bi/connect-data/desktop-directquery-datasets-azure-analysis-s... )

 

(2) When I shared the report to other users, they couldn't see the visuals with data from the direct query dataset.

I have figured out the root cause: When we share report to another user, a "link" will be created and added into the backend dataset. But with composite mode, the link is only added to the "local" dataset, not to the direct query dataset. 

I tired "Live connet" mode and found that PBI can add the link to the source dataset when the report is shared.

So I guess here PBI has a bug. Could you please help to fix it?

 

By the way, seems that PBI currently doesn't support live connect to multiple datasets, is it possible to add this feature? It will be helpful to consolidate reports (just put them together, no data exchange between datasets which we know direct query is needed).

domputer
Frequent Visitor

Lost table relationships when converting Live Connection to Direct Query.

Premium Workspace Dataset from SQL Server Analysis Services database.

Get Data > Power BI Dataset > Table Relationships exist

Make Changes to the Model > Table Relationships disappear except one.

that is not supposed to happen! Can you tell me more about the relationships? Maybe look at the properties over in SSAS to see if any of them have special flags on them?

Please provide additional information regarding finding special flags ?

 

Tried accessing data base directly, same issue
Get Data > SQL Server Analysis Services database > Table Relationships exist
Make Changes to the Model > Table Relationships disappear except one.

you can use any SSAS client tool such as management studio or others to connect to the database. Please check for anything related to private on tables. we have had an issue before where if a table was private it would still be loaded and we have hence fixed it, but wondering if you are experiencing another issue related to it.

Can Microsoft confirm if this is the expected behaviour ?
Workaround after ongoing troubleshooting with user.
Issue related to table key columns being hidden due to Object Level Security being set in Azure SQL Server Analysis Services Database.
Relationships remained after converting from Live Connection to Direct Query when allocated Confidential role access in Azure.
So if a key column has Object level security then all relationships that use that column would be deleted.
Can Microsoft confirm if this is the expected behaviour ?

gabcrep
Regular Visitor

Hi,

 

As mentionned in the limitations of the feature, only users that have Build permission on the datasets can see the report/visuals (4th bullet point):

https://docs.microsoft.com/en-us/power-bi/connect-data/desktop-directquery-datasets-azure-analysis-s...

 

The build permission is not something we necessarly want to grant to any user who wants to consult the «composite» report ... is there any workaround for this limitation?

 

Thanks,

 

Gabriel

 

 

 

 

thanks for the feedback, this is something we're planning to change: just 'read' permissions will be required when we make this feature generally available.

Hi! Do we have any updates regarding the read-only release for using two sets in PRO environments?

we are still waiting on infrastructure changes to happen in the datacenters across the globe before we can make this available to PRO.

Yes! Weird to give changing priviledge to someone would be only reading the dataset outside the original report - a Power BI thin report or in Excel.

hstance
Helper I
Helper I

hstance_1-1658841929777.png

Getting this error in the service after days of developing in desktop with no issue/warning in local refreshes. Very discouraging and wouldn't recommend to anyone to develop in desktop using this feature. I have to now import the datasets I am using instead. I have learned not to use any features in preview going forward if I want to manage expectations well. Preview???? NO THANKS.

I understand that this is annoying - we don't actively stop you from doing this in Desktop as we don't know if you are going to publish to the Service. So instead of "breaking" Desktop for those that never publish to the Service, we allow you to do it and then it breaks when you publish to the Service. If we warned for everything that is not going to work in the Service that would be a very jarring experience and get in the way a lot while it might not even be relevant for you. Please see https://docs.microsoft.com/en-us/power-bi/connect-data/desktop-directquery-datasets-azure-analysis-s... for a list of limitations in this preview, your exact scenario is listed as well.

RickScanlon
Frequent Visitor

It would be great if there were an officially sanctioned and clear approach (or more than one) to managing large datasets (+30GB) using directquery (or not).  This is especially the case because it seems like directquery is currently the best way to deal with huge datasets in PBI. Haven't been able to load huge tables to dataflows, datamart, or blob without timeout errors, etc.  I am fully in the MS ecosystem, so I connect to Azure SQL Database using directquery.  The tables in the DB are indexed (columnstore) and I'm using auto aggregation.  I'm pretty sure that's all I can do (or mostly all), but I'm not entirely sure.  Because it's a little bit of witchcraft.  Would love a video or post like this: dealing with huge datasets from SQL Server et al to PBI. 

This thread isn't related to large models (import or direct query). This is related to connecting to Analysis Services in a Direct Query mode rather than a Live Connection mode.

 

It looks like there are a number of posts under the desktop section of the sight that maybe helpful:

 

As a Consultant myself working with large models (primarily against Snowflake), the advice is to import the data into the model in the first place. with large data this requires implementing incremental refresh. (Note that a P1 capacity has a model size limit of 25GB Capacity and SKUs in Power BI embedded analytics - Power BI | Microsoft Docs.)

 

If you can't scale up the capacity, or reduce data size through optimisation and rationalisation, then utilise direct query with aggregations; auto-aggregations (which may be helpful dependant on the repetitive nature of the queries) or manual aggregations.

 

There is plenty of material on these topics if you Bing search. GuyInACube has some good material as a starting point:

 

gregorykool
Regular Visitor

Hi,
Thanks for adding this feature. Really useful; however we are having some issues at my company. 

As a tenant admin, connecting to a PBI dataset (switched to DirectQuery) + an Excel file is working fine.
But for my colleague (not an admin, but workspace admin), he is getting an error 

"Your credentials could not be authenticated: "Credentials are missing." altough everything is set up correctly in the source (we tried with several kinds). He also enabled the feature in Power BI desktop. 

I checked all the tenant admin settings (mentionned here) too. 
Do you have any idea on what could cause the problem ? 

Thanks for your help

sounds like a permission problem or credentials not being configured for the source. Have you checked the source settings in the Service?

AlejandroErazo
Frequent Visitor

I'm having trouble developing the composite models.
I connect to a powerbi service dataset and create a model in direct query.

I then enabled DirectQuery for PowerBi datasets and the AS option.

Despite this, it doesn't give me the option to connect to any other file.

Also, I went to External Tools and tried to open the Tabular Editor and it gives me an error: The remote server returned an error: (401) Unauthorized

Am I doing something wrong?
Do I need to enable anything else for composite models to work?

 

1.png2.png3.png4.png

 

not sure. Did you restart Desktop after enabling the preview?

Yes, I did. But nothing happens even though I am connected live to the published dataset.

1.png

is this dataset published on Pro/Premium/PPU? Is it not located in "my workspace"?

Helpful resources

Announcements
Carousel_PBI_Wave1

2023 Release Wave 1 Plans

Power BI release plans for 2023 release wave 1 describes all new features releasing from April 2023 through September 2023.

Power BI Summit Carousel 2

Global Power BI Training

Make sure you register today for the Power BI Summit 2023. Don't miss all of the great sessions and speakers!

Thank you 2022 Review

2022 Monthly Feature Releases

We had a great 2022 with a ton of feature releases to help you drive a data culture.