Since last week, when I with Power BI Desktop opened my "thin" PBIX-files that are connected to published DataSets, they only partly completed the opening of the file:
In Report view (upper left icon) it showed a spinning load-symbol, no tables and no graphs.
In Model view (upper left below Report view icono) it showed all Tables and worked as usual. And tables could be dragged to the Layouts.
My suspicion was that it related to my test to assign this DataSet Workspace to a Deployment Pipeline.
Additional characteristics and what I tried:
Opening the thin PBIX never completed. At least not in several hours.
DataSource could'nt be changed in the thin PBIX, because it was busy loading. So I couldn't republish my DataSet PBIX to another/new WorkSpace. (Tough! I have multiple multi-page Reports from this DataSet.)
Creating a new thin PBIX from this DataSet worked! But I couldn't copy all my graphs and formatting from the once above that didn't open, and even if so it would be days of work.
I publish my thin PBIX-files in another WorkSpace/App than the DataSet.
August release of Power BI Desktop installed, but the problem occured with July release too.
This DataSet don't use Row Level Security.
This DataSet don't use Incremental Refresh, but another DataSet in the same WorkSpace do.
This DataSet do have a connection to another DataSet from another WorkSpace, with Import. (Some months ago, this relation used Direct Query, but to avoid the Preview limitation to require Build-access I changed to Import.)
I read about Limitations for Deployment Pipeline, Incremental Refresh, Composite models.
But the solution was to remove the DataSet WorkSpace from the Deployment pipeline, and wait. As I was writing this post to ask for help it started to work. I think it is about 20 hours after I removed the WorkSpace from the Deployment pipeline. Puh!!! What a relief!
I'm good for now, but if anyone can more specifically explain what limitation kicked in it would be interesting to understand. Maybe it was my combinations of used features, and not Deployment Pipeline only.