Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Howdy,
I have a similar problem to this one: https://community.powerbi.com/t5/Report-Server/KPI-s-fail-to-refresh-sometimes-BUG/td-p/207249
We are running Jan 2019 PBIRS
Yesterday, I added a KPI to our PBIRS front page that reports the number of report failures for the day (with trend). This morning the KPI was showing "1" although there were no failures. The corresponding tabular report linked to the same shared dataset shows the correct data. I used VS 2017 to generate toe datasource, dataset and tabular report and published directly from VS to PBIRS.
I then added a second identical KPI and it shows the correct data: "0".
Is this a bug? Do KPI's from shared datasets actually work? Any tips for getting this working?
Same dataset, different result
no caching selected
Unfortunately this is "by design" as we go bitten by this issue too. KPIs always use cached data regardless of that setting on the dataset. The work around is to just setup a scheduled cache refresh. We've just setup a scheduled cache refresh plan that updates the cache every 10 minutes during business hours and it works fine.
Cheers,
Hmmm, this seems *crazy*. I have a paginated report hanging off that same dataset and it refreshes on-demand. I dont have control of cache settings in the KPI tile, so therefore I would have to change the behaviour of the dataset to be cached therefore changing the report to a cached model regardless of the report setting.
Is there a way for me to (from a single dataset) have the KPI operate from caced data as advised, and the report continue to operate in on-demand mode?
Thanks for your help.
@d_gosbell wrote:Unfortunately this is "by design" as we go bitten by this issue too. KPIs always use cached data regardless of that setting on the dataset. The work around is to just setup a scheduled cache refresh. We've just setup a scheduled cache refresh plan that updates the cache every 10 minutes during business hours and it works fine.
Did you eventually solve this problem?
I found out that you always would need a cache with schedule on it for it to refresh
User | Count |
---|---|
7 | |
3 | |
2 | |
2 | |
2 |
User | Count |
---|---|
10 | |
3 | |
3 | |
2 | |
2 |