Forum Discussion
Perspective in a Tabular Model recently broken for anyone else?
I see. If you are using the SSAS connector with the powerbi.com Service, it is likely the same or a similar issue to what I have.
In my case, if I have a dataset using one perspective, and then setup a second connection using a different perspective, the initial dataset changes to reflect the second perspective. Further complicating things, we are using group workspaces where many groups have a perspective targeted toward them. When a dataset in one group "flips" to a different perspective, existing queries still appear to run properly, but attempting to browse and create a new report is a problem. Users can see parts of the model not targeted toward their group's perspective. We are employing row-level security in the tabular model though, so our workaround is simply to use the main model and avoid perspectives for the moment.
Holy Unusable Feature Batman!
Well, that explains a lot, and MANY thanks for revealing that.
Now that I have your excellent analysis I can at least avoid/work around it.
Just hopping on and saying that we see a similar issue as described in some posts above.
Using the web portal, we have a gateway to an on-prem SSAS Tabular instance. When adding a data source using this instance, we get the perspectives all listed separately to choose from. Whichever perspective we choose, we get a new data source added with that perspective's name. When browsing the perspective, regardless of which one was chosen, we observe only the tables exposed in the first defined perspective.
When connecting using Power BI Desktop, perspectives work as they should. When publishing the .pbix with the Tabular datasource, we see the appropriate behavior from the .pbix source in the browser.