Allow mixing direct query and imported tables in a single model

[srinivt]

Allow direct query tables and imported tables to coexist in a single model with ability to create relationships between them.

[nishalit]

Our composite models feature, which lets you combine import and direct query sources in one model, is now generally available with our November release. Read more about it here: https://powerbi.microsoft.com/en-us/blog/power-bi-desktop-november-2018-feature-summary/#compositeModels

[srinivt]

A customer expressed this need through a frown today

[anthonya]

Direct and Import queries need to co-exist

[ANMESTRE]

I have several customers asking for this. When you are using direct query to connect to huge DWs (that is not feasible to import) but at the same time want to join some data from other sources (like Excel) this becomes a critical feature.

[joubin_simoni]

I believe there is a definite need for this functionality to be built into PowerBI. For example, I currently have data I am importing from Oracle that I would like to be via DirectQuery and I need to join it with data from SharePoint lists and Excel (which would be imported) and I am not able to do this. Instead I have to sacrifice performance in order to bring all the needed datasets together.

[johnwatson1985]

This should be possible. It provides much more flexibility if you can choose per source whether you import it or use Direct Query. I also see the possibility to import master data and use direct query for large datasets of transaction data. This ensures fast performance for loading report filters while transaction data is directly queried on demand.

[marek_szulen]

I can't believe, that only a few people need this (and also no comment from the BI team)... This is one of the key functions we need.

[alain_veillette]

We (EXIA) as a Power BI Partner, are giving many training and presentation on Power BI, and this is frequently (if not always) asked: mixing different sources of data in Direct query mode, or mixing tables in Direct query mode with other sources in Import mode. 2 main reasons: 1) Import is not appropriate for large volume of data 2) Direct Query forces you to connect to 1 and only 1 source in the same model.

[hkaalto]

Definitely a needed feature, I have few scenarios where the dataset is simply too big to load into the model so Direct Query is needed but then the customer wants to load some reference Excels for some Ad Hoc data exploration. Applies also the other way around, I have a large dataset which needs to be trimmed so all less frequently required detail information has been stripped away. When the filtering of the data is narrowed down on the report we would need to bring on some details (a long-text) to gain additional insight into the specific class of events. Now this cannot be done as several million longtext-fields would simply break the model data limitation. If that particular visualization could run a Direct Query with some parameters from the filters... I understand the filtering and mapping between a static pre-loaded set and a dynamic one is a bit problematic but allowing to bring in even a limited set of reference data for lookups for either way would enable a lot of scenarios, even if some pieces would be updating asynchronously.

[greg_fleming]

We need this! My data originates from disperate sources.