Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
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:
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.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 6 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |