We are working in a group workspace. While working inside the group from the Power BI service, we add a new data connection to our on-prem SSAS server. Everything works fine. Next, we need to make some changes to our model definition, we need to add some new fields to several tables in the model. We use Visual Studio to make changes to the SSAS model and then deploy those changes. Next we run a refresh and verify the changes look good in Power BI desktop.
Here is the problem, when we go back to the onlne Power BI service and look at the dataset for our SSAS server inside the group workspace, nothing has changed. The new fields we added to tables in the model are not showing up on the Power BI service view. We tried t orefresh the data from the Power BI service, refresh the browser, log off and back on and still the changes never appeared in the dataset for our SSAS connection. Out of curiousity we create a duplicate connection to the SSAS model and the changes are there in the new connection but not in the old connection. If this is an active connection to the SSAS service, why is it not showing model definition changes?
Imagine building many reports off a model and at some point you are told, you need to add new semesters or date periods to a date dimension. You need to incorporate those changes in existing reports. If the Power BI service doesn't recoginize changes to a model in SSAS then you are dead in the water. If you want to delete and recreate the dataset to get the changes, you will lose every report tied to that existing dataset.
This probelm does not exist in the Power BI desktop. Only when working with a dataset inside a workspace group in the Power BI service does this problem exist. The only reason we are working within the workspace group is so we have a single publishing point for reports, where all of the editing capabilities are shared.
For the time being, we are just publishing reports to our personal workspace and then sharing it with the group workspace, which is not ideal.
This did bring up another interesting question for consideration though. If everything you do happens inside a group workspace, and you create many reports off a single dataset, what happens if somebody in that group comes along and deletes a dataset tied to all of your reports? I know you can restrict permissions in a group but what if its one of your power users who does this. Either way you would be in bad shape since I can see no way to recover that kind of data in Power BI. If you were publishing to your local workspace you would at least have another copy you could share again with the group. This has led me to reconsider working exclusively from inside a group workspace.
I'd be curious if you see this as a risk or how you might consider working around the data loss issue. This is probably something fit for another thread.
Hi SDP, I raised a ticket for our issue that looks to be exactly the same core problem, I have not had a reply yet:
There are core issues with dashboards tiles not updating when using the SSAS connector, even though the underlying reports update correctly after pressing the refresh button. These issues are interrelated and manifest differently with the iOS app, Android app and main website. I think the key cause is using dynamic time intelligence as a report filter, but secondarily with rebuilding the reports and repining the tiles.
I have setup the reports in the following manner:
Each report has a DashBoard with the same name that have tiles pinned from the underlying report. All reports have a single Dataset using the latest SSAS connector. The main difference between the reports above is a report level filter using time intelligence within SSAS to create a dynamic filter. Eg XYZ Client V4.1 Today has a filter TODAY that is a dimension hierarchy on the main date time dimension for the tabular model. The TODAY hierarchy automatically calculates the date for the today and displays the data automatically. Similarly, XYZ Client V4.1 Yesterday does the same filtering for YESTERDAY and each report for their respective time period. The reason for this is so that users, especially using the mobile apps, can access the right report pre-filtered for the date period. The SSAS tabular model is fully reprocessed at the beginning of each day, and then partially reprocessed during the day for data updates. We are using Groups to display the reports to the right set of end users, and the users are members only to stop editing.
The problem is that the tiles do not automatically update once pinned and the behaviour is different depending upon the Power BI client used:
Overall to try to mitigate this behaviour, I have updated the SSAS connector and even restart it after the full SSAS reprocess. Nothing makes any difference to the behaviour described.
To provide a meaningful Power BI experience I suggest:
If you want a test user to reproduce the behaviour, please ask and I will quickly setup this.
Currently Power BI is not being used by many users as it simply is not consistently updating for them. I also cannot rollout to our external customers without a consistent refresh behaviour.