Forum Discussion
Advocate IIs it really not possible to publish report changes without overwriting the dataset?
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.
Advocate Iedhans - My apologies for not clarifying.
This is in Power BI Desktop. I have the original, let's call this PBI1, pbix file (containing the report and dataset), that same file I opened and saved as a new name, let's call this PBI2, in the same directory. So at this point I've got two pbix's that are both report/dataset but just with different names.
I open PBI2, delete all the tables in the model causing the visuals to error out. At this point, to get my data back again I go to "Get Data -> Power BI dataset" and that's when I got the error about it not allowing me to do so.
Please let me know if I'm not being clear enough
Community ChampionNot 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.
- pbi-ai
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?
- edhans
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.