Forum Discussion
Is it really not possible to publish report changes without overwriting the dataset?
- 4 years ago
Not sure. Here is what I did, and it just worked 5min ago.
- I have the DQ Connection to Power BI Datasets turned on in preview. This isn't necessary but the steps are a bit different.
- Saved my full PBIX as Report Name Thin Test.pbix.
- Went to Model View. Selected all tables and deleted them.
- Connected to Power BI Datasets.
- Checked the box next to the dataset I wanted to get all tables (this is what is new in the DQ Dataset preview)
- Pressed ok.
After about a minute, all visuals started working again. Save the file and it is a less than 2MB PBIX file, because virtually nothing is in it.
edhans - That "DirectQuery for Power BI datasets and AS" setting was what I was missing. It worked after this. Thank you very much
I see now that this is essentially a live/direct query connection to the dataset itself (the table boxes in the model view have a blue line over it). This really shouldn't affect performance or anything, right?
Correct with one HUGE caveat. If you add additional tables from other datasets into the report, and join them in the composite model, you will see performance issues in these cross-island relationships.
But with one dataset - it is the same thing as a single Power BI dataset. You are just using the model's engine.