Publishing report creates a secondary dataset

[filip_u_s]

Hi all.

I Created a dataset where I prepare the excel data for consumption... and then I created two reports with a direct query to this dataset.
But the weird part is that when I publish one of the reports it creates a secondary dataset between the dataset and the report. (See image)

I checked and the secondary dataset got an hourly refreshrate... while the first dataset has a manual refreshrate.

First... Why does the publication of the report creates a dataset with an hourly refreshrate, when it's based on the dataset with the manual setting?

Second... even if I turn off the hourly refreshrate on the secondary dataset... I can't remove it without removing the dataset... is there anyway to get PowerBI to get that it doesn't need that set and remove it?

(p.s. the excelfile only updates once a month, so an hourly refresh rate is just wasted capacity)

[filip_u_s · Accepted solution]

After some experimenting I actually manage to fix it this time.

It turned out that the Direct Query connection I had made the publication of the report create a secondary dataset.

I went into "Transform data" and removed the data connection, after which I closed and saved the transformation.
After that I went into "Get data" and selected a "Power BI-datasets" connection and connected it again to the main source.
When I the published the report it created a new report without a secondary dataset.

Not really sure what kind of DirectQuery connection I had from the beginning... but sure seems the way you connect to the data makes the difference.