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
Hi @soldous - yes they did get to the bottom of it! For our org this was fixed by enabling the tenant setting (we only did this for specific users): Allow XMLA endpoints and Analyze in Excel with on-premises datasets
This is the feature we are been waiting for for literally years, thank you! However, it doesn't seem to work, does something need to be enabled on our tenant?
Specifically I have enabled the preview feature, restarted Power BI desktop and connected to one of my Power BI datasets (in fact a few of them) but all the options to import data are greyed out as it always used to be. I also don't see the "make changes to this model" link in the bottom right as described in the video. A colleague of mine has also tried but the same thing.
@frostystoo Not all models are supported (for example SSAS, even if published to the PBI Service). Can you make sure your dataset is supported by checking the limitations section here: DirectQuery for Power BI datasets and Azure Analysis Services (preview) | Microsoft Power BI Blog | ...
If you believe it should be, please share some additional details/screenshots to help us identify the problem.
First of all thanks for this amazing future, I have seen the demo ( during MBAS 2020... I think ) and was waiting for the preview with anticipation.
I do have a few questions I hope you will be able to answer:
While connecting to two datasets Sales and Order ( both star schemas ) and both datasets/models contains the same dimension Product:
1. Can you give more info on the data sources you are connected to for Product and Product 2?
2. I don't believe so, but perhaps @jeroenterheerdt can help answer your question about performance.
3. This is an interesting idea. We don't allowe for that right now, but can you describe a bit more about your expected behavior?
4. When this feature is GA it will be available for both shared and premium.
I have the same question as Mariusz, and I think it gets at architectural issues that Power BI has with conformed dimensions. It's never been clear to me the best way to handle them as there is no concept of shared dimensions like there used to be in SSAS MD.
If there's two models, both with a copy of the same Product dimension and those two models are "composited" together, you're going to have two Product dimensions. How do you get the two models to work together across this dimension? Can you remove one? Can you link them together somehow? It seems to me that each model may contain its own measures with references to its own Product dimension. How do we keep these working?
Well, is this realy related to "Composite"? Same question with "Import"...
The usual way is to have just one dim with several relations and to build measures with "USERALTIONSHIP".
I'm not sure I follow you. I'm talking about multiple models, not multiple tables within a single model.
Model A has a star schema that includes Product dimension.
Model B has a star schema that includes Product dimension.
Model C is a composite of A and B. C now contains Product(A) and Product(B). What's the right way of handling this situation?
@tessahurr I am not sure who @jeroent is, but that's not me 🙂 regarding the performance question from @Mariusz: if I understand it correctly you are asking if there is performance difference between filtering within one source compared to across two sources. While the answer is it depends, I would expect the performance for filtering across two sources to be less than within the source, unless one of the tables is significantly larger than the other.
This is a brilliant enhancement with huge potential value - thank you.
Note however, preview testing I have an issue in desktop importing a PBI dataset into a simple existing local model (i.e. composite model) where the table relationships from this "live connection" dataset were lost when using this method importing as direct query. The imported PBI dataset tables are all shown in the Model view and data can be obtained from each individually - however these tables have no relationships and neither can the original relationships be re-added, so the dataset model cannot really be used.
I'm not sure this is due to the nature of the preview version, a current table limitation or something I am doing incorrectly - does anyone have any suggestions?
Great announcement! Thanks Power BI team!
1 - I was testing how many online dataset I was able to add to a single model. Seems that 2 is maximum right now. When trying to add a 3rd, I'm getting the following error message: "Sequence contains more than one element".
2 - It would be really nice to have the tables with the same color the model is. If it's crowded it will be nice to quickly and visually identify or match model with corresponding tables.
Im getting issue publishing the report.
"An error occurred while attempting to publish xxxx
Publishing failed for an unkown reason.
I get the same error message with a Power BI dataset whose storage mode I changed from Live to Direct Query (Mixed).
In Live mode, the upload works normally - just like with other datasets (Import, Live, ...).
So I didnt do any thing special. I just connect to TWO powerbi Dataset and add excel file.
Create relationships. But when i publish im getting the error of
Also RELATED formula is not working. even i have a Many is to 1 relationship.
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.